From: Michael Spradling <mike@mspradling.com>
To: kernel-janitors@vger.kernel.org
Subject: Re: [PATCH 1/1] Removed Dead Code
Date: Wed, 18 Nov 2009 12:11:03 +0000 [thread overview]
Message-ID: <20091118121103.GC22619@MSServer> (raw)
In-Reply-To: <20091117053847.GA19184@MSServer>
I know it takes more than a day to take a patch in, however I just wanted to know
a little more about the process. Sorry about the 3 emails. If you look at the
headers you will notice they are all from different email accounts. I had trouble
with my email and I did not see my messages post to the mailing list. Thanks for
your advice and input....
I was just wondering how one checks the status of it.
On Wed, Nov 18, 2009 at 01:01:51PM +0100, Bernd Petrovitsch wrote:
> On Tue, 2009-11-17 at 19:12 -0500, Michael Spradling wrote:
> > Does anyone have any comments, how do I know if this patch is ever taken in...
> Yes (but perhaps not the one you expected;-).
> A review takes usually more than a day (since people tend to have other,
> higher priorities too). And BTW it doesn't speed up if you send the same
> 3 times without good reason (and if there is a good reason, there is no
> need to hide it). And the subject as above is *much* better (as it
> describes the intentions of the patch and not your personal ones) than
> the one on the 1st mail.
>
> A good way to speed up the review process is to send the mail also
> directly to the relevant maintainers and interested people (and probably
> the big kernel-mailinglist. No need to subscribe it - it is expected
> that people use Reply-to-all and not delete any Cc:s - unless you really
> know what you do[0]). The simplest way is to use
> scripts/get_maintainer.pl to get a list of probably interested and
> *relevant* (read: subsystem maintainer) people/mailing-lists.
>
> Even if 5 people review and ack-it hereover, it is no help as long as
> the maintainer(s) ignore it (or NACK it for whatever reason).
>
> As for the patch as such: Not that I looked into the framebuffer
> driver(s) or anywhere else, but it's probably good to also mention why
> you believe that that functions are dead code.
> There basically two possibilities: Was in for ages and isn't used any
> longer or is needed for new features. And the subsystem maintainer
> should know (and I don't know - so I can't comment on it) .....
>
> > Is there a server somewhere that shows integration status
> Not until you run one;-)
> You usually should get some feedback who is taking it and - depending on
> subsystem, it's maintainer, the length of the chain towards Linux,
> release dates, etc. - it eventually shows up in mainline and you may get
> some status mails before (e.g. AKPM has scripts which also report
> towards submitters - and reviewers IIRC).
>
> Bernd
>
> [0]: *If* you really know what you do, you will know it on your own.
> Before, just stick to the rule;-)
> --
> Firmix Software GmbH http://www.firmix.at/
> mobil: +43 664 4416156 fax: +43 1 7890849-55
> Embedded Linux Development and Services
>
>
next prev parent reply other threads:[~2009-11-18 12:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-17 5:38 [PATCH 1/1] Removed Dead Code Michael Spradling
2009-11-17 6:04 ` Michael Spradling
2009-11-17 6:10 ` Michael Spradling
2009-11-18 0:12 ` Michael Spradling
2009-11-18 9:05 ` Nicolas Palix
2009-11-18 12:01 ` Bernd Petrovitsch
2009-11-18 12:11 ` Michael Spradling [this message]
2009-11-18 12:13 ` Michael Spradling
2009-11-18 12:37 ` Bernd Petrovitsch
2009-11-18 17:31 ` Davidlohr Bueso
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=20091118121103.GC22619@MSServer \
--to=mike@mspradling.com \
--cc=kernel-janitors@vger.kernel.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