From: Andrew Lunn <andrew@lunn.ch>
To: Greg KH <greg@kroah.com>
Cc: b.a.t.m.a.n@lists.open-mesh.net
Subject: Re: [B.A.T.M.A.N.] [PATCH 0/3] Staging: Batman-adv: Bug fixes for 2.6.34-rc2.
Date: Fri, 30 Apr 2010 07:03:44 +0200 [thread overview]
Message-ID: <20100430050344.GG3734@lunn.ch> (raw)
In-Reply-To: <20100429193015.GA18882@kroah.com>
On Thu, Apr 29, 2010 at 12:30:15PM -0700, Greg KH wrote:
> On Mon, Mar 22, 2010 at 10:46:12PM +0100, Andrew Lunn wrote:
> > Hi Greg
> >
> > Here are three patches against 2.6.34-rc2 which we would like including
> > into the next -rc kernel. All three are bug fixes, with the first being a
> > regression relative to 2.6.33 and the second two being older bugs, prescent
> > in 2.6.33.
>
> In looking at these more, they are a bit too big to take now for 2.6.34.
> The first one is a regression, which is fine, but you also fixed up code
> at the same time, which I can't take this late in the merge cycle.
>
> So, mind if I just push these for .35, and then add them to .34 through
> the -stable tree for .34 when that opens up?
That is O.K.
Do i need to repost them to stable@kernel.org?
Thanks
Andrew
next prev parent reply other threads:[~2010-04-30 5:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-22 21:46 [B.A.T.M.A.N.] [PATCH 0/3] Staging: Batman-adv: Bug fixes for 2.6.34-rc2 Andrew Lunn
2010-03-22 21:46 ` [B.A.T.M.A.N.] [PATCH 1/3] Staging: batman-adv: don't have interrupts disabled while sending Andrew Lunn
2010-03-22 21:46 ` [B.A.T.M.A.N.] [PATCH 2/3] Staging: batman-adv: Fix VIS output bug for secondary interfaces Andrew Lunn
2010-03-22 21:46 ` [B.A.T.M.A.N.] [PATCH 3/3] Staging: batman-adv: Fixing wrap-around bug in vis Andrew Lunn
2010-04-29 19:30 ` [B.A.T.M.A.N.] [PATCH 0/3] Staging: Batman-adv: Bug fixes for 2.6.34-rc2 Greg KH
2010-04-30 5:03 ` Andrew Lunn [this message]
2010-04-30 14:45 ` Greg KH
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=20100430050344.GG3734@lunn.ch \
--to=andrew@lunn.ch \
--cc=b.a.t.m.a.n@lists.open-mesh.net \
--cc=b.a.t.m.a.n@lists.open-mesh.org \
--cc=greg@kroah.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