From: "John W. Linville" <linville@tuxdriver.com>
To: "Luis R. Rodriguez" <mcgrof@gmail.com>
Cc: Javier Cardona <javier@cozybit.com>,
linux-wireless@vger.kernel.org,
Andrey Yurovsky <andrey@cozybit.com>,
stable@kernel.org, johannes@sipsolutions.net
Subject: Re: [PATCH 1/2] mac80211: Fixed bug in mesh portal paths
Date: Thu, 10 Dec 2009 07:58:48 -0500 [thread overview]
Message-ID: <20091210125848.GA11112@tuxdriver.com> (raw)
In-Reply-To: <43e72e890912092220k4525d40bn680afece3e8cbb52@mail.gmail.com>
On Wed, Dec 09, 2009 at 10:20:03PM -0800, Luis R. Rodriguez wrote:
> On Wed, Dec 9, 2009 at 6:43 PM, Javier Cardona <javier@cozybit.com> wrote:
> > Paths to mesh portals were being timed out immediately after each use in
> > intermediate forwarding nodes. mppath->exp_time is set to the expiration time
> > so assigning it to jiffies was marking the path as expired.
> >
> > Signed-off-by: Javier Cardona <javier@cozybit.com>
> > Signed-off-by: Andrey Yurovsky <andrey@cozybit.com>
>
> Is Cc: stable@kernel.org required or does actually CC'ing
> stable@kernel.org in the patch suffice? If the patch has the CC
> embedded on the commit log I thought stable team would be notified
> upon a merge of the patch. Please correct me if I'm wrong.
>
> Would like to verify as I'm going to be a stable whore now.
AIUI either is acceptable. But adding the Cc line in the commit log
aids the stable team in automating their process.
In any case, sending stuff to stable@kernel.org is highly recommended
(within their guidelines, of course).
John
--
John W. Linville Someday the world will need a hero, and you
linville@tuxdriver.com might be all we have. Be ready.
prev parent reply other threads:[~2009-12-10 13:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-10 2:43 [PATCH 1/2] mac80211: Fixed bug in mesh portal paths Javier Cardona
2009-12-10 2:43 ` [PATCH 2/2] mac80211: Revert 'Use correct sign for mesh active path refresh' Javier Cardona
2009-12-10 6:20 ` [PATCH 1/2] mac80211: Fixed bug in mesh portal paths Luis R. Rodriguez
2009-12-10 12:58 ` John W. Linville [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=20091210125848.GA11112@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=andrey@cozybit.com \
--cc=javier@cozybit.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=mcgrof@gmail.com \
--cc=stable@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;
as well as URLs for NNTP newsgroup(s).