public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Chenbo Feng <fengc@google.com>
Cc: joel@joelfernandes.org,
	Alexei Starovoitov <alexei.starovoitov@gmail.com>,
	Daniel Colascione <dancol@google.com>,
	Joel Fernandes <joelaf@google.com>,
	linux-kernel@vger.kernel.org, Tim Murray <timmurray@google.com>,
	netdev@vger.kernel.org, Lorenzo Colitti <lorenzo@google.com>,
	Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
	Alexei Starovoitov <ast@fb.com>,
	Daniel Borkmann <daniel@iogearbox.net>,
	stable@vger.kernel.org
Subject: Re: [PATCH v4] Wait for running BPF programs when updating map-in-map
Date: Sat, 10 Nov 2018 07:22:32 -0800	[thread overview]
Message-ID: <20181110152232.GA24724@kroah.com> (raw)
In-Reply-To: <CAMOXUJ=YFEwzBdkQw8xUrQXd4ZRzX6ob0dOCCRA=uEbjvw9yEQ@mail.gmail.com>

On Fri, Nov 09, 2018 at 06:01:54PM -0800, Chenbo Feng wrote:
> Hi netdev,
> 
> Could we queue up this patch to stable 4.14 and stable 4.19? I can
> provide a backport patch if needed. I checked it is a clean
> cherry-pick for 4.19 but have some minor conflict for 4.14.

What is the git commit id of the patch in Linus's tree?

thanks

greg k-h

  reply	other threads:[~2018-11-11  1:07 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20180816040145.gqzqicab4s6kcbye@ast-mbp.dhcp.thefacebook.com>
     [not found] ` <20181012105427.243779-1-dancol@google.com>
     [not found]   ` <20181013023138.m445q6itdmyxdtoc@ast-mbp.dhcp.thefacebook.com>
2018-10-16 17:39     ` [PATCH v4] Wait for running BPF programs when updating map-in-map Joel Fernandes
2018-10-18 15:46       ` Alexei Starovoitov
2018-10-18 23:36         ` Joel Fernandes
2018-11-10  2:01           ` Chenbo Feng
2018-11-10 15:22             ` Greg KH [this message]
2018-11-10 18:58               ` Chenbo Feng

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=20181110152232.GA24724@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=alexei.starovoitov@gmail.com \
    --cc=ast@fb.com \
    --cc=dancol@google.com \
    --cc=daniel@iogearbox.net \
    --cc=fengc@google.com \
    --cc=joel@joelfernandes.org \
    --cc=joelaf@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lorenzo@google.com \
    --cc=mathieu.desnoyers@efficios.com \
    --cc=netdev@vger.kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=timmurray@google.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