From: Andrew Morton <akpm@linux-foundation.org>
To: Seth Forshee <seth.forshee@canonical.com>
Cc: "Kirill A. Shutemov" <kirill@shutemov.name>,
Hugh Dickins <hughd@google.com>,
Chris Down <chris@chrisdown.name>,
Amir Goldstein <amir73il@gmail.com>,
Heiko Carstens <hca@linux.ibm.com>,
Vasily Gorbik <gor@linux.ibm.com>,
Christian Borntraeger <borntraeger@de.ibm.com>,
linux-mm@kvack.org, linux-s390@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] tmpfs: Disallow CONFIG_TMPFS_INODE64 on s390
Date: Mon, 8 Feb 2021 09:48:38 -0800 [thread overview]
Message-ID: <20210208094838.74c7ca910a16f33aacacb4b0@linux-foundation.org> (raw)
In-Reply-To: <YCE3cjDNOvpeCCeA@ubuntu-x1>
On Mon, 8 Feb 2021 07:06:58 -0600 Seth Forshee <seth.forshee@canonical.com> wrote:
> On Sun, Feb 07, 2021 at 05:48:31PM +0300, Kirill A. Shutemov wrote:
> > On Fri, Feb 05, 2021 at 05:06:20PM -0600, Seth Forshee wrote:
> > > This feature requires ino_t be 64-bits, which is true for every
> > > 64-bit architecture but s390, so prevent this option from being
> > > selected there.
> >
> > Quick grep suggests the same for alpha. Am I wrong?
>
> No, it appears you are right. Looks like my grep missed alpha somehow.
>
> Andrew, do you prefer an additional patch or an updated version of the
> previous patch?
Doesn't matter much. A second patch for Alpha would be best, I guess.
Thanks.
prev parent reply other threads:[~2021-02-08 17:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-05 23:06 Seth Forshee
2021-02-06 0:05 ` Andrew Morton
2021-02-06 0:40 ` Chris Down
2021-02-07 12:17 ` Heiko Carstens
2021-02-08 22:50 ` Hugh Dickins
2021-02-07 14:48 ` Kirill A. Shutemov
2021-02-08 13:06 ` Seth Forshee
2021-02-08 17:48 ` Andrew Morton [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210208094838.74c7ca910a16f33aacacb4b0@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=amir73il@gmail.com \
--cc=borntraeger@de.ibm.com \
--cc=chris@chrisdown.name \
--cc=gor@linux.ibm.com \
--cc=hca@linux.ibm.com \
--cc=hughd@google.com \
--cc=kirill@shutemov.name \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-s390@vger.kernel.org \
--cc=seth.forshee@canonical.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox