From: NeilBrown <neilb@suse.de>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: "J. Bruce Fields" <bfields@fieldses.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Ben Hutchings <ben@decadent.org.uk>,
linux-nfs@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arch@vger.kernel.org
Subject: Re: [PATCH] All Arch: remove linkage for sys_nfsservctl system call
Date: Tue, 30 Aug 2011 09:11:50 +1000 [thread overview]
Message-ID: <20110830091150.176cd08c@notabene.brown> (raw)
In-Reply-To: <20110830085752.6db1ffa600f4c82135b3f3eb@canb.auug.org.au>
On Tue, 30 Aug 2011 08:57:52 +1000 Stephen Rothwell <sfr@canb.auug.org.au>
wrote:
> Hi Bruce,
>
> On Fri, 26 Aug 2011 18:03:11 -0400 "J. Bruce Fields" <bfields@fieldses.org> wrote:
> >
> > From: NeilBrown <neilb@suse.de>
> >
> > The nfsservctl system call is now gone, so we should remove all
> > linkage for it.
> >
> > Signed-off-by: NeilBrown <neilb@suse.de>
> > Signed-off-by: J. Bruce Fields <bfields@redhat.com>
> > ---
> >
> > I don't normally have to deal with this kind of cross-architecture
> > patch; is this the right etiquette for it?
>
> It turns out (with hindsight) that my reaction to this patch should have
> been:
>
> If you haven't built this on all architectures (an noone expects you to
> actually do that), then it should spend a day or two in linux-next before
> being sent to Linus.
>
Hi Stephen,
Thanks for your help in sorting this out. I have no idea how I missed those
few nfsservctl references but I clearly did and you and -next have proved
valuable yet again.
And really *everything* should spend a few days in linux-next before going
to Linus. We all know that but it sometimes seem hard to *do* that ....
until we have learnt the hard way a couple of times :-(
Thanks,
NeilBrown
next prev parent reply other threads:[~2011-08-29 23:12 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1312810169.2591.1153.camel@deadeye>
[not found] ` <20110808155538.GB904@fieldses.org>
[not found] ` <20110808180658.GC29924@decadent.org.uk>
[not found] ` <20110808180658.GC29924-/+tVBieCtBitmTQ+vhA3Yw@public.gmane.org>
2011-08-26 22:03 ` [PATCH] All Arch: remove linkage for sys_nfsservctl system call J. Bruce Fields
2011-08-26 22:03 ` J. Bruce Fields
2011-08-26 23:32 ` Ben Hutchings
[not found] ` <20110826233258.GE24107-/+tVBieCtBitmTQ+vhA3Yw@public.gmane.org>
2011-08-26 23:52 ` J. Bruce Fields
2011-08-26 23:52 ` J. Bruce Fields
2011-08-27 0:01 ` David Miller
2011-08-27 14:39 ` Mike Frysinger
2011-08-28 21:12 ` David Miller
2011-08-28 23:50 ` Tony Breeds
2011-08-28 23:50 ` Tony Breeds
[not found] ` <20110826220311.GA18140-uC3wQj2KruNg9hUCZPvPmw@public.gmane.org>
2011-08-29 22:57 ` Stephen Rothwell
2011-08-29 22:57 ` Stephen Rothwell
2011-08-29 23:11 ` NeilBrown [this message]
[not found] ` <20110830091150.176cd08c-wvvUuzkyo1EYVZTmpyfIwg@public.gmane.org>
2011-08-31 13:46 ` J. Bruce Fields
2011-08-31 13:46 ` J. Bruce Fields
2011-08-31 10:15 ` David Howells
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=20110830091150.176cd08c@notabene.brown \
--to=neilb@suse.de \
--cc=ben@decadent.org.uk \
--cc=bfields@fieldses.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=torvalds@linux-foundation.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).