From: Sergey Shtylyov <s.shtylyov@auroraos.dev>
To: Jakub Kicinski <kuba@kernel.org>
Cc: Andrew Lunn <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>, <linux-usb@vger.kernel.org>,
<netdev@vger.kernel.org>
Subject: Re: [PATCH] r8152: simplify loops in generic_ocp_{read,write}()
Date: Sun, 23 Aug 2026 11:37:11 +0300 [thread overview]
Message-ID: <f68c123f-12d2-4704-b9f0-a26d17ae87de@auroraos.dev> (raw)
In-Reply-To: <20260822135832.274fe2a4@kernel.org>
On 8/22/26 11:58 PM, Jakub Kicinski wrote:
[...]
>> And of course I forgot [net-next] in the subject... :-)
>
> And to check if it's open ;)
> https://netdev.bots.linux.dev/net-next.html
I don't do much netdev these days, so I just forgot the usual
routine (and I couldn't wait so much with posting the patch anyway).
Is it still possible to send net-next stuff with [RFC] added to
the subject while net-next is closed?
As I'll have to do v2 anyway, I'll try to wait for net-next to
open before posting it...
[...]
MBR, Sergey
next prev parent reply other threads:[~2026-08-23 8:37 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-22 20:21 [PATCH] r8152: simplify loops in generic_ocp_{read,write}() Sergey Shtylyov
2026-08-22 20:26 ` Sergey Shtylyov
2026-08-22 20:58 ` Jakub Kicinski
2026-08-23 8:37 ` Sergey Shtylyov [this message]
2026-08-24 17:59 ` Jakub Kicinski
2026-08-22 21:03 ` Michal Pecio
2026-08-23 8:16 ` David Laight
2026-08-24 16:00 ` Sergey Shtylyov
2026-08-23 7:52 ` Sergey Shtylyov
2026-08-23 8:11 ` David Laight
[not found] ` <4a7604ab-c6ef-4552-b63b-3e7146ff42d0@auroraos.dev>
2026-08-23 9:51 ` David Laight
2026-08-23 18:00 ` Sergey Shtylyov
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=f68c123f-12d2-4704-b9f0-a26d17ae87de@auroraos.dev \
--to=s.shtylyov@auroraos.dev \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
/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