From: Greg KH <greg@kroah.com>
To: Antonio Quartulli <ordex@autistici.org>
Cc: b.a.t.m.a.n@lists.open-mesh.org
Subject: Re: [B.A.T.M.A.N.] batman-adv stable patches: information request
Date: Tue, 22 Nov 2011 14:48:44 -0800 [thread overview]
Message-ID: <20111122224844.GC26340@kroah.com> (raw)
In-Reply-To: <20111122224700.GA26340@kroah.com>
On Tue, Nov 22, 2011 at 02:47:00PM -0800, Greg KH wrote:
> On Mon, Nov 21, 2011 at 10:27:10PM +0100, Antonio Quartulli wrote:
> > Hello Greg,
> >
> > On Mon, Nov 21, 2011 at 12:54:22 -0800, Greg KH wrote:
> > > On Mon, Nov 21, 2011 at 08:27:24PM +0100, Antonio Quartulli wrote:
> > > > Hello Greg,
> > > >
> > > > I'm Antonio Quartulli, a net/batman-adv kernel module contributor, and I'm
> > > > contacting you as you are the stable tree maintainer.
> > > >
> > > > On Oct 25, 2011 I sent the following two patches to stable@kernel.org:
> > > >
> > > > - [PATCH 1/2] batman-adv: fix tt_local_reset_flags() function
> > > > which is 31901264511cf20c5ed33b8649a3ca9ce28df60b in David's net-next branch
> > > >
> > > >
> > > > - [PATCH 2/2] batman-adv: correctly set the data field in the TT_REPONSE packet
> > > > which is 9d8523931f7f5eb8900077f0da0fbe6b8ad0010b in David's net-next branch
> > > >
> > > > Up to now we didn't received any reply, either ACK or NACK, but I saw that
> > > > linux-3.1.1 has been released in the meanwhile. As I guessed, this release
> > > > doesn't contain our patches.
> > > >
> > > > Did I miss something in the stable-submit procedure?
> > > > I'm sorry for any inconvenient but this is the first time that I send patches to
> > > > stable.
> > >
> > > Ugh, no, you did everything right, it's just that at that point in time,
> > > stable@kernel.org was down, as it still is, the new address is
> > > stable@vger.kernel.org.
> > >
> >
> > Ah ok, thank you for the advice!
> >
> > At this point we have 3 patches more that we sent to the wrong address after the
> > two that I already mentioned. The patches are:
> >
> > - [PATCH 1/3] batman-adv: remove references for global tt entries
> > commit id in Dadiv's tree: 531027fcddbcf81c9937dd04f08a7e8f11fd47d2
> >
> > - [PATCH 2/3] batman-adv: add sanity check when removing global tts
> > commit id in Dadiv's tree: 6e8014947d6469df1566e9e253805557c5c0e4e0
> >
> > - [PATCH 3/3] batman-adv: unify hash_entry field position in
> > tt_local/global_entry
> > commit id in Dadiv's tree: 93840ac40bb0d0f177ef8af74e64671be67e8c37
> >
> > > I'll queue these two patches up for the next release. Just to verify,
> > > these should only go to 3.1-stable, and not 3.0-stable as well?
> > >
> >
> > Exactly: the 5 patches are for 3.1-stable only.
>
> The 2/3 patch above did apply to the 3.0-stable tree, but I didn't
> include it there, let me know if you want me to.
Oh nevermind, it didn't apply properly, I should have looked more
carefully.
greg k-h
prev parent reply other threads:[~2011-11-22 22:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-21 19:27 [B.A.T.M.A.N.] batman-adv stable patches: information request Antonio Quartulli
2011-11-21 20:54 ` Greg KH
2011-11-21 21:27 ` Antonio Quartulli
2011-11-22 22:47 ` Greg KH
2011-11-22 22:48 ` Greg KH [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=20111122224844.GC26340@kroah.com \
--to=greg@kroah.com \
--cc=b.a.t.m.a.n@lists.open-mesh.org \
--cc=ordex@autistici.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