From: Christoph Hellwig <hch@infradead.org>
To: Eric Sandeen <sandeen@redhat.com>
Cc: "Darrick J. Wong" <darrick.wong@oracle.com>,
linux-xfs <linux-xfs@vger.kernel.org>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] xfs: mark ARM OABI as incompatible in Kconfig
Date: Tue, 25 Feb 2020 09:56:17 -0800 [thread overview]
Message-ID: <20200225175617.GB4129@infradead.org> (raw)
In-Reply-To: <79faa339-d6b8-d8eb-0857-7d755a780805@redhat.com>
On Mon, Feb 24, 2020 at 04:58:20PM -0800, Eric Sandeen wrote:
> Yeah probably.
>
> But now looking at
>
> aa2dd0ad4d6d xfs: remove __arch_pack
>
> hch indicates that some non-arm architectures have similar problems,
> so is there any point to excluding this one config on this one arch?
Yes, I think we just need to be more careful with our newly added
structure layouts and whenever we do a major reorganization of an
existing one.
prev parent reply other threads:[~2020-02-25 17:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-25 0:49 [PATCH] xfs: mark ARM OABI as incompatible in Kconfig Eric Sandeen
2020-02-25 0:55 ` Darrick J. Wong
2020-02-25 0:58 ` Eric Sandeen
2020-02-25 17:56 ` Christoph Hellwig [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=20200225175617.GB4129@infradead.org \
--to=hch@infradead.org \
--cc=darrick.wong@oracle.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-xfs@vger.kernel.org \
--cc=sandeen@redhat.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