From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: "Marek Szyprowski" <m.szyprowski@samsung.com>,
bpf@vger.kernel.org, netdev@vger.kernel.org,
"David S. Miller" <davem@davemloft.net>,
"Alexei Starovoitov" <ast@kernel.org>,
"Daniel Borkmann" <daniel@iogearbox.net>,
"Eric Dumazet" <edumazet@google.com>,
"Jakub Kicinski" <kuba@kernel.org>,
"Jesper Dangaard Brouer" <hawk@kernel.org>,
"John Fastabend" <john.fastabend@gmail.com>,
"Thomas Gleixner" <tglx@linutronix.de>,
"Toke Høiland-Jørgensen" <toke@toke.dk>,
"Toke Høiland-Jørgensen" <toke@redhat.com>,
linux-mips@vger.kernel.org
Subject: Re: [PATCH net-next v3 2/3] net: dev: Makes sure netif_rx() can be invoked in any context.
Date: Tue, 22 Feb 2022 17:13:26 +0100 [thread overview]
Message-ID: <YhULprI8YK7YxFo9@linutronix.de> (raw)
In-Reply-To: <alpine.DEB.2.22.394.2202221622570.372449@ramsan.of.borg>
On 2022-02-22 16:30:37 [+0100], Geert Uytterhoeven wrote:
> Hi Sebastian,
Hi Geert,
> Similar on rbtx4927 (CONFIG_NE2000=y), where I'm getting a slightly
> different warning:
Based on the backtrace the patch in
https://lore.kernel.org/all/Yg05duINKBqvnxUc@linutronix.de/
should fix it, right?
Sebastian
next prev parent reply other threads:[~2022-02-22 16:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220211233839.2280731-1-bigeasy@linutronix.de>
[not found] ` <20220211233839.2280731-3-bigeasy@linutronix.de>
[not found] ` <CGME20220216085613eucas1p1d33aca0243a3671ed0798055fc65dc54@eucas1p1.samsung.com>
[not found] ` <da6abfe2-dafd-4aa1-adca-472137423ba4@samsung.com>
2022-02-22 15:30 ` [PATCH net-next v3 2/3] net: dev: Makes sure netif_rx() can be invoked in any context Geert Uytterhoeven
2022-02-22 16:13 ` Sebastian Andrzej Siewior [this message]
2022-02-23 7:56 ` Geert Uytterhoeven
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=YhULprI8YK7YxFo9@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=geert@linux-m68k.org \
--cc=hawk@kernel.org \
--cc=john.fastabend@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=netdev@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=toke@redhat.com \
--cc=toke@toke.dk \
/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