All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Sven Eckelmann <sven@narfation.org>
Cc: Sasha Levin <sashal@kernel.org>,
	hdanton@sina.com, sw@simonwunderlich.de, stable@vger.kernel.org
Subject: Re: FAILED: patch "[PATCH] batman-adv: Don't schedule OGM for disabled interface" failed to apply to 4.4-stable tree
Date: Wed, 18 Mar 2020 15:26:52 +0100	[thread overview]
Message-ID: <20200318142652.GA2807628@kroah.com> (raw)
In-Reply-To: <2953272.8TNtrSRRcZ@bentobox>

On Wed, Mar 18, 2020 at 03:20:11PM +0100, Sven Eckelmann wrote:
> On Wednesday, 18 March 2020 15:17:50 CET Sasha Levin wrote:
> > >From 8e8ce08198de193e3d21d42e96945216e3d9ac7f Mon Sep 17 00:00:00 2001
> > >From: Sven Eckelmann <sven@narfation.org>
> > >Date: Sun, 16 Feb 2020 13:02:06 +0100
> > >Subject: [PATCH] batman-adv: Don't schedule OGM for disabled interface
> > >
> > >A transmission scheduling for an interface which is currently dropped by
> > >batadv_iv_ogm_iface_disable could still be in progress. The B.A.T.M.A.N. V
> > >is simply cancelling the workqueue item in an synchronous way but this is
> > >not possible with B.A.T.M.A.N. IV because the OGM submissions are
> > >intertwined.
> > >
> > >Instead it has to stop submitting the OGM when it detect that the buffer
> > >pointer is set to NULL.
> [...]
> > Adjusted context and queued up for 4.4.
> 
> There are most likely patches missing again when you only added this single 
> patch. See the 48 patches I've sent yesterday for batman-adv in 4.4.

Yeah, I'll queue these all up later on today, thank you for the series.

greg k-h

  reply	other threads:[~2020-03-18 14:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-16 13:45 FAILED: patch "[PATCH] batman-adv: Don't schedule OGM for disabled interface" failed to apply to 4.4-stable tree gregkh
2020-03-18 14:17 ` Sasha Levin
2020-03-18 14:20   ` Sven Eckelmann
2020-03-18 14:26     ` Greg KH [this message]
2020-03-18 20:54       ` Sasha Levin

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=20200318142652.GA2807628@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=hdanton@sina.com \
    --cc=sashal@kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=sven@narfation.org \
    --cc=sw@simonwunderlich.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.