From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Steven Whitehouse <swhiteho@redhat•com>
Cc: linux-next@vger•kernel.org, linux-kernel@vger•kernel.org,
linux-fsdevel@vger•kernel.org, Alexander Viro <aviro@redhat•com>,
Adrian Bunk <bunk@kernel•org>,
Andrew Morton <akpm@linux-foundation•org>,
"David S. Miller" <davem@davemloft•net>
Subject: Re: fs: Make linux kernel parser's match_table_t const
Date: Sat, 16 Aug 2008 18:35:36 +1000 [thread overview]
Message-ID: <20080816183536.47dbfae6.sfr@canb.auug.org.au> (raw)
In-Reply-To: <1218808842.20622.130.camel@quoit>
[-- Attachment #1: Type: text/plain, Size: 1087 bytes --]
Hi Steven,
On Fri, 15 Aug 2008 15:00:42 +0100 Steven Whitehouse <swhiteho@redhat•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@canb•auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
prev parent reply other threads:[~2008-08-16 8:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-15 14:00 fs: Make linux kernel parser's match_table_t const Steven Whitehouse
2008-08-16 8:35 ` Stephen Rothwell [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=20080816183536.47dbfae6.sfr@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=akpm@linux-foundation$(echo .)org \
--cc=aviro@redhat$(echo .)com \
--cc=bunk@kernel$(echo .)org \
--cc=davem@davemloft$(echo .)net \
--cc=linux-fsdevel@vger$(echo .)kernel.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=swhiteho@redhat$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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