[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20080816183536.47dbfae6.sfr@canb.auug.org.au>
Date: Sat, 16 Aug 2008 18:35:36 +1000
From: Stephen Rothwell <sfr@...b.auug.org.au>
To: Steven Whitehouse <swhiteho@...hat.com>
Cc: linux-next@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-fsdevel@...r.kernel.org, Alexander Viro <aviro@...hat.com>,
Adrian Bunk <bunk@...nel.org>,
Andrew Morton <akpm@...ux-foundation.org>,
"David S. Miller" <davem@...emloft.net>
Subject: Re: fs: Make linux kernel parser's match_table_t const
Hi Steven,
On Fri, 15 Aug 2008 15:00:42 +0100 Steven Whitehouse <swhiteho@...hat.com> wrote:
>
> Unlike the previous version, I've put the "const" by the individual
> variable declarations, all aside from the nfsroot one that is
> which was the cause of the problems. That is marked as __initconst
> instead.
A much better approach - hiding the "const" in the typedef was always a
bit strange.
> Is this trivial enough for the trivial tree, or is there a better
> place for it, VFS tree, or direct into linux-next for example?
linux-next currently has no easy way to include single patches like
this. An alternative approach would be to ask Linus to take just the
changes to match_token() into his tree now (as they are clearly correct
and don't adversely affect any other code) and then send all the other
bits to each of the maintainers. That way we avoid possible conflicts in
linux-next over the following months and during the next merge window.
--
Cheers,
Stephen Rothwell sfr@...b.auug.org.au
http://www.canb.auug.org.au/~sfr/
Content of type "application/pgp-signature" skipped
Powered by blists - more mailing lists