All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Joe Stringer <joe@ovn.org>
Cc: davem@davemloft.net, Pravin B Shelar <pshelar@nicira.com>,
	stable@vger.kernel.org, stable-commits@vger.kernel.org
Subject: Re: Patch "openvswitch: Fix helper reference leak" has been added to the 4.3-stable tree
Date: Wed, 6 Jan 2016 15:07:52 -0800	[thread overview]
Message-ID: <20160106230752.GA15928@kroah.com> (raw)
In-Reply-To: <CAPWQB7H-ZTvmsq4L9H+V-0sK7GJ3gM2QVXeKwp4afJV76unJ+w@mail.gmail.com>

On Wed, Jan 06, 2016 at 11:45:44AM -0800, Joe Stringer wrote:
> On 30 December 2015 at 19:53,  <gregkh@linuxfoundation.org> wrote:
> >
> > This is a note to let you know that I've just added the patch titled
> >
> >     openvswitch: Fix helper reference leak
> >
> > to the 4.3-stable tree which can be found at:
> >     http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
> >
> > The filename of the patch is:
> >      openvswitch-fix-helper-reference-leak.patch
> > and it can be found in the queue-4.3 subdirectory.
> >
> > If you, or anyone else, feels it should not be added to the stable tree,
> > please let <stable@vger.kernel.org> know about it.
> 
> <snip>
> 
> [catching up on emails, apologies for the delay..]
> 
> The patch mentioned above had another issue, this patch fixes it:
> https://patchwork.ozlabs.org/patch/560757/

A patch needs to be in Linus's tree before I can do anything with it for
a stable release...

      reply	other threads:[~2016-01-06 23:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-31  3:53 Patch "openvswitch: Fix helper reference leak" has been added to the 4.3-stable tree gregkh
2016-01-06 19:45 ` Joe Stringer
2016-01-06 23:07   ` 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=20160106230752.GA15928@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=davem@davemloft.net \
    --cc=joe@ovn.org \
    --cc=pshelar@nicira.com \
    --cc=stable-commits@vger.kernel.org \
    --cc=stable@vger.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 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.