From: Dan Carpenter <dan.carpenter@oracle.com>
To: Mike Marshall <hubcap@omnibond.com>
Cc: Martin Brandenburg <martin@omnibond.com>,
Christophe JAILLET <christophe.jaillet@wanadoo.fr>,
LKML <linux-kernel@vger.kernel.org>,
kernel-janitors@vger.kernel.org
Subject: Re: [PATCH] orangefs: Axe some dead code
Date: Mon, 28 Nov 2016 17:36:27 +0300 [thread overview]
Message-ID: <20161128143627.GT6266@mwanda> (raw)
In-Reply-To: <CAOg9mST9iVfz9ipu4svSqiWXZzwp2w=kOyR+Aww=NbcaGeR7dA@mail.gmail.com>
On Mon, Nov 28, 2016 at 09:06:12AM -0500, Mike Marshall wrote:
> Perhaps we should modify Greg KH's "be-all, end-all document"
> on "HOWTO do Linux kernel development" then... you've
> contributed a boatload of work to the kernel since as far
> back as 2006, but I'm a newbie who just works in an
> isolated subsystem... people like me need a reliable
> and authoritative cheat-sheet to go by...
>
> I think you believe I should ask for this to be pulled only
> during a merge window. Since this patch doesn't involve new
> functionality, or even any functionality, it seems like pull-fodder
> anytime after it is vetted, based on Greg's HOWTO...
Hm. Yes. I can see how that document is misleading. I'll send a
patch.
>
> My original intent on posting to this thread was to let
> christophe.jaillet@wanadoo.fr know that I saw and
> appreciate his review and the good patch he supplied.
>
Yes. Of course. But this discussion has been valuable, I hope.
regards,
dan carpenter
prev parent reply other threads:[~2016-11-28 14:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-21 22:17 [PATCH] orangefs: Axe some dead code Christophe JAILLET
2016-11-22 15:49 ` Martin Brandenburg
2016-11-24 12:31 ` Mike Marshall
2016-11-25 21:51 ` Dan Carpenter
2016-11-25 23:09 ` Mike Marshall
2016-11-26 10:02 ` Dan Carpenter
2016-11-26 13:51 ` Mike Marshall
2016-11-28 11:07 ` Dan Carpenter
2016-11-28 14:06 ` Mike Marshall
2016-11-28 14:36 ` Dan Carpenter [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=20161128143627.GT6266@mwanda \
--to=dan.carpenter@oracle.com \
--cc=christophe.jaillet@wanadoo.fr \
--cc=hubcap@omnibond.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin@omnibond.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