From: Christoph Hellwig <hch@infradead.org>
To: bugzilla-daemon@bugzilla.kernel.org
Cc: linux-ext4@vger.kernel.org
Subject: Re: [Bug 42986] ext2_fs.h requires undefined type umode_t
Date: Tue, 27 Mar 2012 03:31:28 -0400 [thread overview]
Message-ID: <20120327073128.GA974@infradead.org> (raw)
In-Reply-To: <201203270533.q2R5Xl42031625@bugzilla.kernel.org>
On Tue, Mar 27, 2012 at 05:33:47AM +0000, bugzilla-daemon@bugzilla.kernel.org wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=42986
>
>
>
>
>
> --- Comment #8 from H. Peter Anvin <hpa@zytor.com> 2012-03-27 05:33:47 ---
> That's fine, but it's also a gratuitous change to previously working userspace.
> It sounds like the right thing would be to leave <linux/ext2_fs.h> in place
> exporting only those constants as a backwards compatibility measure.
That's probably a good idea, given how widespread people use the flags.
next prev parent reply other threads:[~2012-03-27 7:31 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-24 13:23 [Bug 42986] New: ext2_fs.h requires undefined type umode_t bugzilla-daemon
2012-03-24 14:04 ` [Bug 42986] " bugzilla-daemon
2012-03-24 14:16 ` bugzilla-daemon
2012-03-25 1:20 ` bugzilla-daemon
2012-03-25 2:47 ` bugzilla-daemon
2012-03-25 17:21 ` bugzilla-daemon
2012-03-27 4:41 ` bugzilla-daemon
2012-03-27 5:02 ` bugzilla-daemon
2012-03-27 5:33 ` bugzilla-daemon
2012-03-27 7:31 ` Christoph Hellwig [this message]
2012-03-27 5:58 ` bugzilla-daemon
2012-03-27 6:05 ` bugzilla-daemon
2012-03-27 6:17 ` bugzilla-daemon
2012-03-27 6:21 ` bugzilla-daemon
2012-04-12 11:37 ` bugzilla-daemon
2012-04-12 15:04 ` bugzilla-daemon
2012-04-13 6:48 ` bugzilla-daemon
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=20120327073128.GA974@infradead.org \
--to=hch@infradead.org \
--cc=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-ext4@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).