From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: jbaron@redhat.com, linux-kernel@vger.kernel.org, joe@perches.com,
greg@kroah.com, nick@nick-andrew.net, randy.dunlap@oracle.com
Subject: Re: [PATCH 2/7] dynamic debug v2 - nfs conversion
Date: Tue, 15 Jul 2008 18:56:07 -0400 [thread overview]
Message-ID: <1216162567.7981.82.camel@localhost> (raw)
In-Reply-To: <20080715154323.b7d5f14d.akpm@linux-foundation.org>
On Tue, 2008-07-15 at 15:43 -0700, Andrew Morton wrote:
> On Tue, 15 Jul 2008 18:30:03 -0400
> Trond Myklebust <trond.myklebust@fys.uio.no> wrote:
>
> > On Tue, 2008-07-15 at 17:32 -0400, Jason Baron wrote:
> > > -convert sunrpc debug facility
> > >
> > > Signed-off-by: Jason Baron <jbaron@redhat.com>
> > >
> >
> > Where the hell did this come from, what's its purpose, and WTF haven't
> > you Cced linux-nfs@vger.kernel.org so that the rest of us can review it?
>
> It's on linux-kernel. If you don't have a linux-kernel subscription
> then you should fix that. Set up a procmail rule and do a
> search-by-subject when needed.
I get my daily share of 1000-odd mails from linux-kernel, thanks, but
99% of that goes into the trashcan. I only keep a mail if I see that
it's relevant. In this case, 1 email out of 7 turns out to be relevant
(after I inadvertently deleted the apparently crucial first 2 emails),
and there is no changelog entry to tell me what's being done or why.
By Ccing the correct list, we at least get a heads-up that this thread
might be important. I can't archive all of lkml on my laptop, but I can
and do archive all of linux-nfs...
> In this case, yes, it would have been nice if Jason had cc'ed lots of
> different lists and individuals on the core patch and then selectively
> cc'ed lists and individuals on the per-subsystem followup patches. But
> I doubt if even 2% of patch submitters manage to do all that correctly.
The point is that he is changing a semi-official interface for tracing
the NFS kernel activity from userspace. I'd like to know why and how it
is being modified before I can ack it.
In addition there are several other developers who have a daily interest
in using this interface when helping our users, and who might have
comments.
Trond
next prev parent reply other threads:[~2008-07-15 22:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-15 21:32 [PATCH 2/7] dynamic debug v2 - nfs conversion Jason Baron
2008-07-15 22:30 ` Trond Myklebust
2008-07-15 22:43 ` Andrew Morton
2008-07-15 22:56 ` Trond Myklebust [this message]
2008-07-15 23:08 ` Andrew Morton
2008-07-15 23:15 ` Trond Myklebust
2008-07-15 23:24 ` Andrew Morton
2008-07-15 23:44 ` Trond Myklebust
2008-07-16 19:58 ` Jason Baron
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=1216162567.7981.82.camel@localhost \
--to=trond.myklebust@fys.uio.no \
--cc=akpm@linux-foundation.org \
--cc=greg@kroah.com \
--cc=jbaron@redhat.com \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nick@nick-andrew.net \
--cc=randy.dunlap@oracle.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