From: Jarek Poplawski <jarkao2@gmail.com>
To: Dan Williams <dcbw@redhat.com>
Cc: "Paoloni, Gabriele" <gabriele.paoloni@intel.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"paulus@samba.org" <paulus@samba.org>
Subject: Re: PATCH_ppp_mp_explode_redesign
Date: Tue, 7 Apr 2009 09:43:26 +0000 [thread overview]
Message-ID: <20090407094325.GA6031@ff.dom.local> (raw)
In-Reply-To: <1239052276.28824.26.camel@localhost.localdomain>
On 06-04-2009 23:11, Dan Williams wrote:
> On Mon, 2009-04-06 at 17:38 +0100, Paoloni, Gabriele wrote:
>> Hi
>>
>> Can anybody tell me what is the procedure that is followed to apply the patch and when it will be officially released.
>
> Dave Miller (networking maintainer) applied your patch to his various
> trees on March 13th. Since 2.6.29 was in bug-fix only mode at that
> time, your patch was too late to be included 2.6.29. It has just been
> merged into Linus' linux-2.6 tree [1] (which will become 2.6.30) via
> Dave Miller's tree. So it appears your patch will be included in the
> 2.6.30 kernel when that is released.
>
> If you think your patch is regression-free and appropriate for stable
> kernels (2.6.27, 2.6.28, etc) you might try to send it to the stable
> team for inclusion in subsequent stable kernel updates.
I guess it's preferred here to ask David for sending to -stable yet
(and it usually needs merging to the net-2.6 tree first).
Jarek P.
prev parent reply other threads:[~2009-04-07 9:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-03 11:55 PATCH_ppp_mp_explode_redesign gabriele.paoloni
2009-03-13 23:09 ` PATCH_ppp_mp_explode_redesign David Miller
2009-03-19 11:57 ` PATCH_ppp_mp_explode_redesign Paoloni, Gabriele
2009-04-06 16:38 ` PATCH_ppp_mp_explode_redesign Paoloni, Gabriele
2009-04-06 21:11 ` PATCH_ppp_mp_explode_redesign Dan Williams
2009-04-07 9:43 ` Jarek Poplawski [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=20090407094325.GA6031@ff.dom.local \
--to=jarkao2@gmail.com \
--cc=dcbw@redhat.com \
--cc=gabriele.paoloni@intel.com \
--cc=netdev@vger.kernel.org \
--cc=paulus@samba.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.