All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Howells <dhowells@redhat.com>
To: Jakub Kicinski <kuba@kernel.org>
Cc: dhowells@redhat.com, netdev@vger.kernel.org,
	linux-afs@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net 0/4] rxrpc: Fixes ver #2
Date: Mon, 03 Feb 2020 19:38:54 +0000	[thread overview]
Message-ID: <1004693.1580758734@warthog.procyon.org.uk> (raw)
In-Reply-To: <20200203103914.4b038cb7@cakuba.hsd1.ca.comcast.net>

Jakub Kicinski <kuba@kernel.org> wrote:

> I pulled rxrpc-fixes-20200202 since that tag seems to correspond to 
> the patches on the mailing list.

Sorry, yes - I forgot to change that.

> Should I queue these for stable? There are some fixes to fixes here, 
> so AFAIK we need:
> 
> 5273a191dca65a675dc0bcf3909e59c6933e2831   4.9+
> 04d36d748fac349b068ef621611f454010054c58   4.19+
> f71dbf2fb28489a79bde0dca1c8adfb9cdb20a6b   4.9+
> fac20b9e738523fc884ee3ea5be360a321cd8bad   4.19+

Yes, please.  DaveM asked me not to put stable tags in my net patches, IIRC,
as his scripts do that automagically.

David


  parent reply	other threads:[~2020-02-03 19:39 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-03 10:30 [PATCH net 0/4] rxrpc: Fixes ver #2 David Howells
2020-02-03 10:30 ` [PATCH net 1/4] rxrpc: Fix use-after-free in rxrpc_put_local() " David Howells
2020-02-03 10:30 ` [PATCH net 2/4] rxrpc: Fix insufficient receive notification generation " David Howells
2020-02-03 10:31 ` [PATCH net 3/4] rxrpc: Fix missing active use pinning of rxrpc_local object " David Howells
2020-02-03 10:31 ` [PATCH net 4/4] rxrpc: Fix NULL pointer deref due to call->conn being cleared on disconnect " David Howells
2020-02-03 18:39 ` [PATCH net 0/4] rxrpc: Fixes " Jakub Kicinski
2020-02-03 19:38 ` David Howells [this message]
2020-02-03 20:28   ` Jakub Kicinski

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=1004693.1580758734@warthog.procyon.org.uk \
    --to=dhowells@redhat.com \
    --cc=kuba@kernel.org \
    --cc=linux-afs@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@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.