DPDK patches and discussions
 help / color / mirror / Atom feed
From: Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>
To: Ferruh Yigit <ferruh.yigit@xilinx.com>,
	Stephen Hemminger <stephen@networkplumber.org>
Cc: dev@dpdk.org, Min Hu <humin29@huawei.com>,
	mingli.yu@windriver.com, Jiri Slaby <jslaby@suse.cz>,
	stable@dpdk.org
Subject: Re: [PATCH v3] kni: fix build with Linux 5.18
Date: Sun, 5 Jun 2022 11:20:27 +0300	[thread overview]
Message-ID: <83ff8e0b-f5de-f821-ba05-66443c9c28f4@oktetlabs.ru> (raw)
In-Reply-To: <20220605075449.3095576-1-andrew.rybchenko@oktetlabs.ru>

On 6/5/22 10:54, Andrew Rybchenko wrote:
> From: Jiri Slaby <jslaby@suse.cz>
> 
> Since commit 2655926aea9b (net: Remove netif_rx_any_context() and
> netif_rx_ni().) in 5.18, netif_rx_ni() no longer exists as netif_rx()
> can be called from any context. So define HAVE_NETIF_RX_NI for older
> releases and call the appropriate function in kni_net.
> 
> Cc: stable@dpdk.org
> 
> Signed-off-by: Jiri Slaby <jslaby@suse.cz>
> Signed-off-by: Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>

Self NACK. I've found correct patch in patchwork finally.

      reply	other threads:[~2022-06-05  8:20 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-25 10:12 [PATCH] " Jiri Slaby
2022-05-25 10:26 ` [PATCH v2] " Jiri Slaby
2022-05-31 16:25   ` Ferruh Yigit
2022-06-01  6:51   ` [PATCH v3] " Jiri Slaby
2022-06-01  6:53     ` [PATCH v4] " Jiri Slaby
2022-06-05  8:22       ` Andrew Rybchenko
2022-06-06  5:59         ` Jiri Slaby
2022-06-06 16:20           ` Andrew Rybchenko
2022-06-06 10:46         ` [PATCH] kni: fix build Thomas Monjalon
2022-06-05  7:54 ` [PATCH v3] kni: fix build with Linux 5.18 Andrew Rybchenko
2022-06-05  8:20   ` Andrew Rybchenko [this message]

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=83ff8e0b-f5de-f821-ba05-66443c9c28f4@oktetlabs.ru \
    --to=andrew.rybchenko@oktetlabs.ru \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@xilinx.com \
    --cc=humin29@huawei.com \
    --cc=jslaby@suse.cz \
    --cc=mingli.yu@windriver.com \
    --cc=stable@dpdk.org \
    --cc=stephen@networkplumber.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;
as well as URLs for NNTP newsgroup(s).