All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Cc: Sasha Levin <sashal@kernel.org>,
	linux-kernel@vger.kernel.org, stable@vger.kernel.org,
	Antonio Quartulli <a@unstable.cc>,
	Marek Lindner <mareklindner@neomailbox.ch>,
	Simon Wunderlich <sw@simonwunderlich.de>,
	Sven Eckelmann <sven@narfation.org>,
	b.a.t.m.a.n@lists.open-mesh.org,
	"David S. Miller" <davem@davemloft.net>,
	Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [PATCH 5.15] batman-adv: Use netif_rx_any_context() any.
Date: Sat, 23 Jul 2022 17:19:47 +0200	[thread overview]
Message-ID: <YtwRk2OVuALT3khr@kroah.com> (raw)
In-Reply-To: <YtbW7Ca3t4/3qB7k@linutronix.de>

On Tue, Jul 19, 2022 at 06:08:12PM +0200, Sebastian Andrzej Siewior wrote:
> This reverts the stable commit
>    e65d78b12fbc0 ("batman-adv: Use netif_rx().")
> 
> The commit message says:
> 
> | Since commit
> |    baebdf48c3600 ("net: dev: Makes sure netif_rx() can be invoked in any context.")
> |
> | the function netif_rx() can be used in preemptible/thread context as
> | well as in interrupt context.
> 
> This commit (baebdf48c3600) has not been backported to the 5.15 stable
> series and therefore, the commit which builds upon it, must not be
> backported either.
> 
> Revert the backport and use netif_rx_any_context() again.
> 
> Signed-off-by: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
> ---
>  net/batman-adv/bridge_loop_avoidance.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)

Now queued up, thanks.

greg k-h

  reply	other threads:[~2022-07-23 15:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-19 16:08 [PATCH 5.15] batman-adv: Use netif_rx_any_context() any Sebastian Andrzej Siewior
2022-07-23 15:19 ` Greg Kroah-Hartman [this message]
2022-07-23 15:19 ` Patch "batman-adv: Use netif_rx_any_context() any." has been added to the 5.15-stable tree gregkh

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=YtwRk2OVuALT3khr@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=a@unstable.cc \
    --cc=b.a.t.m.a.n@lists.open-mesh.org \
    --cc=bigeasy@linutronix.de \
    --cc=davem@davemloft.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mareklindner@neomailbox.ch \
    --cc=sashal@kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=sven@narfation.org \
    --cc=sw@simonwunderlich.de \
    --cc=tglx@linutronix.de \
    /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.