Linux kernel -stable discussions
 help / color / mirror / Atom feed
From: Julian Wiedmann <jwi@linux.ibm.com>
To: Sasha Levin <sashal@kernel.org>
Cc: stable-commits@vger.kernel.org,
	Julian Wiedmann <jwi@linux.ibm.com>,
	stable@vger.kernel.org
Subject: Re: Patch "s390/qeth: strictly order bridge address events" has been added to the 5.8-stable tree
Date: Mon, 26 Oct 2020 10:16:08 +0200	[thread overview]
Message-ID: <4617e1c2-d791-3a18-9cfb-953589ab6c29@linux.ibm.com> (raw)
In-Reply-To: <20201026053517.556992085B@mail.kernel.org>

On 26.10.20 07:35, Sasha Levin wrote:
> This is a note to let you know that I've just added the patch titled
> 
>     s390/qeth: strictly order bridge address events
> 
> to the 5.8-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:
>      s390-qeth-strictly-order-bridge-address-events.patch
> and it can be found in the queue-5.8 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.
> 

This requires
commit a04f0ecacdb0 ("s390/qeth: don't let HW override the configured port role").

> 
> 
> commit fb538911d11db15ff92e0588cba365eb92c9d4f2
> Author: Julian Wiedmann <jwi@linux.ibm.com>
> Date:   Thu Aug 27 10:17:05 2020 +0200
> 
>     s390/qeth: strictly order bridge address events
>     
>     [ Upstream commit 9d6a569a4cbab5a8b4c959d4e312daeecb7c9f09 ]
>     

[...]

       reply	other threads:[~2020-10-26  8:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20201026053517.556992085B@mail.kernel.org>
2020-10-26  8:16 ` Julian Wiedmann [this message]
2020-10-26 14:38   ` Patch "s390/qeth: strictly order bridge address events" has been added to the 5.8-stable tree 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=4617e1c2-d791-3a18-9cfb-953589ab6c29@linux.ibm.com \
    --to=jwi@linux.ibm.com \
    --cc=sashal@kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox