From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Pavel Fedin <sonic_amiga@rambler.ru>
Cc: linuxppc-dev list <linuxppc-dev@ozlabs.org>
Subject: Re: [PATCH] Non-DMA mode for floppy on PowerPC
Date: Wed, 23 Feb 2005 12:59:22 +1100 [thread overview]
Message-ID: <1109123962.5412.164.camel@gaston> (raw)
In-Reply-To: <20050222130646.25bc9520.sonic_amiga@rambler.ru>
On Tue, 2005-02-22 at 13:06 -0500, Pavel Fedin wrote:
> On Tue, 22 Feb 2005 01:32:09 -0800
> Eugene Surovegin <ebs@ebshome.net> wrote:
>
> > Please, be patient and don't repost the same stuff every day.
>
> Ok. How long does it take for a patch to get included into the kernel? I
> posted if two weeks ago for the first time and nothing happened. In LKML also nobody answers.
Maybe you haven't noticed but 2.6.11 is actually in late -rc phase and
not open to such patches.
Just be patient. Patches posted to linuxppc-dev or linuxppc64-dev are
generally not lost as we have an automatic patch tracking system there.
It will be picked up at one point.
Also, it's a good habit, _especially_ if you re-post your patch, to
actually repost it properly re-based against the latest linux bk tree,
or at least the latest -rc, and with the proper format (which is -p1),
maintainers just don't have time to play at fixing patches.
Ben.
next prev parent reply other threads:[~2005-02-23 2:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-22 17:18 [PATCH] Non-DMA mode for floppy on PowerPC Pavel Fedin
2005-02-22 9:32 ` Eugene Surovegin
2005-02-22 18:06 ` Pavel Fedin
2005-02-22 15:56 ` Hollis Blanchard
2005-02-22 17:54 ` Eugene Surovegin
2005-02-23 1:59 ` Benjamin Herrenschmidt [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-02-21 21:49 Pavel Fedin
2005-02-15 15:31 Pavel Fedin
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=1109123962.5412.164.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=sonic_amiga@rambler.ru \
/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).