All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sven Eckelmann <sven@narfation.org>
To: David Miller <davem@davemloft.net>,
	Networking <netdev@vger.kernel.org>,
	Stephen Rothwell <sfr@canb.auug.org.au>
Cc: "Linux Next Mailing List" <linux-next@vger.kernel.org>,
	"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
	"Linus Lüssing" <linus.luessing@c0d3.blue>,
	"Simon Wunderlich" <sw@simonwunderlich.de>
Subject: Re: linux-next: Fixes tag needs some work in the net tree
Date: Mon, 21 Sep 2020 08:04:30 +0200	[thread overview]
Message-ID: <1845864.bm72gKIjWm@ripper> (raw)
In-Reply-To: <20200921055919.5bf70643@canb.auug.org.au>

[-- Attachment #1: Type: text/plain, Size: 1351 bytes --]

On Sunday, 20 September 2020 21:59:19 CEST Stephen Rothwell wrote:
> Hi all,

Yes, I've accidentally swapped the IDs while adding them to the various patches.

The correct ones should have been:

* 097930e85f90 ("batman-adv: bla: fix type misuse for backbone_gw hash indexing")

  Fixes: 07568d0369f9 ("batman-adv: don't rely on positions in struct for hashing")
  (seems to be correct)

* 7dda5b338412 ("batman-adv: mcast/TT: fix wrongly dropped or rerouted packets")

  Fixes: 279e89b2281a ("batman-adv: bla: use netif_rx_ni when not in interrupt context")
  (seems to be correct)

* 4bba9dab86b6 ("batman-adv: Add missing include for in_interrupt()")

  Fixes: 279e89b2281a ("batman-adv: bla: use netif_rx_ni when not in interrupt context")
  (seems to be correct)

* 3236d215ad38 ("batman-adv: mcast: fix duplicate mcast packets in BLA backbone from LAN")

  Fixes: a44ebeff6bbd ("batman-adv: Fix multicast TT issues with bogus ROAM flags")
  (this was wrong)

* 74c09b727512 ("batman-adv: mcast: fix duplicate mcast packets in BLA backbone from mesh")

  Fixes: 2d3f6ccc4ea5 ("batman-adv: check incoming packet type for bla")
  (this was wrong)

* 2369e8270469 ("batman-adv: mcast: fix duplicate mcast packets from BLA backbone to mesh")

  Fixes: fe2da6ff27c7 ("batman-adv: add broadcast duplicate check")
  (this was wrong)

Kind regards,
	Sven

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2020-09-21  6:04 UTC|newest]

Thread overview: 83+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-20 19:59 linux-next: Fixes tag needs some work in the net tree Stephen Rothwell
2020-09-21  6:04 ` Sven Eckelmann [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-05-05 22:01 Stephen Rothwell
2024-03-18 21:14 Stephen Rothwell
2023-12-19 20:57 Stephen Rothwell
2023-06-12 22:45 Stephen Rothwell
2023-04-02 22:03 Stephen Rothwell
2022-08-31  6:38 Stephen Rothwell
2022-08-25  5:59 Stephen Rothwell
2022-03-03  9:33 Stephen Rothwell
2022-02-27 20:20 Stephen Rothwell
2022-01-17  2:22 Stephen Rothwell
2021-11-22 21:00 Stephen Rothwell
2021-10-27 20:42 Stephen Rothwell
2021-09-10 12:50 Stephen Rothwell
2021-08-22 21:54 Stephen Rothwell
2021-08-24  2:12 ` Shreyansh Chouhan
2021-08-24  2:29   ` Stephen Rothwell
2021-08-16 21:56 Stephen Rothwell
2021-07-13 22:26 Stephen Rothwell
2021-07-14  8:29 ` Pavel Skripkin
2021-07-08 21:31 Stephen Rothwell
2021-07-08 21:38 ` Florian Fainelli
2021-07-08 21:44   ` Eric Dumazet
2021-07-08 21:45     ` Florian Fainelli
2021-06-24 21:45 Stephen Rothwell
2021-06-07 22:53 Stephen Rothwell
2021-06-08  6:23 ` Ido Schimmel
2021-06-08  8:53   ` Petr Machata
2021-05-25 22:33 Stephen Rothwell
2021-05-04 21:57 Stephen Rothwell
2021-03-21 20:48 Stephen Rothwell
2021-03-15 21:57 Stephen Rothwell
2021-03-04  3:19 Stephen Rothwell
2020-08-17  5:53 Stephen Rothwell
2020-04-22 22:06 Stephen Rothwell
2020-04-02 20:59 Stephen Rothwell
2020-03-04  5:08 Stephen Rothwell
2020-02-19 20:33 Stephen Rothwell
2020-02-18 20:45 Stephen Rothwell
2020-01-19  1:06 Stephen Rothwell
2020-01-10  8:15 Stephen Rothwell
2020-01-08 10:10 Stephen Rothwell
2020-01-03  3:38 Stephen Rothwell
2019-11-20  9:50 Stephen Rothwell
2019-11-20 14:14 ` Willem de Bruijn
2019-11-07 10:04 Stephen Rothwell
2019-10-30  7:37 Stephen Rothwell
2019-10-27 20:13 Stephen Rothwell
2019-10-11  4:11 Stephen Rothwell
2019-10-11 20:06 ` Keller, Jacob E
2019-09-28 18:51 Stephen Rothwell
2019-08-18 21:33 Stephen Rothwell
2019-08-11 21:33 Stephen Rothwell
2019-08-06 21:22 Stephen Rothwell
2019-07-12  6:50 Stephen Rothwell
2019-07-14  7:55 ` Tariq Toukan
2019-07-14 12:15   ` Stephen Rothwell
2019-07-14 12:17     ` Tariq Toukan
2019-06-23 21:47 Stephen Rothwell
2019-06-24  1:51 ` Voon, Weifeng
2019-06-10 18:37 Stephen Rothwell
2019-05-30 21:52 Stephen Rothwell
2019-05-23 21:35 Stephen Rothwell
2019-05-19  1:55 Stephen Rothwell
2019-05-05 21:23 Stephen Rothwell
2019-04-28  6:49 Stephen Rothwell
2019-04-11 21:12 Stephen Rothwell
2019-04-12  7:19 ` Ursula Braun
2019-04-11  6:58 Stephen Rothwell
2019-04-11  7:24 ` Jason Wang
2019-04-11  7:37   ` David Miller
2019-04-11  7:56     ` Jason Wang
2019-03-29  3:26 Stephen Rothwell
2019-03-29 16:46 ` Jeff Kirsher
2019-03-19 21:15 Stephen Rothwell
2019-03-20  7:26 ` Kalle Valo
2019-03-20  9:45 ` Lorenzo Bianconi
2019-03-19  5:20 Stephen Rothwell
2019-02-28 20:32 Stephen Rothwell
2019-02-12 20:04 Stephen Rothwell
2019-02-10 20:14 Stephen Rothwell
2019-01-20  4:10 Stephen Rothwell

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=1845864.bm72gKIjWm@ripper \
    --to=sven@narfation.org \
    --cc=davem@davemloft.net \
    --cc=linus.luessing@c0d3.blue \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    --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.