From: Jakub Kicinski <kuba@kernel.org>
To: Jonathan Corbet <corbet@lwn.net>
Cc: Bagas Sanjaya <bagasdotme@gmail.com>,
Florian Fainelli <f.fainelli@gmail.com>,
Paolo Abeni <pabeni@redhat.com>,
Casper Andersson <casper.casan@gmail.com>,
Andrew Lunn <andrew@lunn.ch>,
Heiner Kallweit <hkallweit1@gmail.com>,
Russell King <linux@armlinux.org.uk>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
netdev@vger.kernel.org, linux-doc@vger.kernel.org
Subject: Re: [PATCH net-next] docs: networking: phy: add missing space
Date: Wed, 5 Oct 2022 17:14:48 -0700 [thread overview]
Message-ID: <20221005171448.21c8c595@kernel.org> (raw)
In-Reply-To: <8735c2bbqt.fsf@meer.lwn.net>
On Wed, 05 Oct 2022 08:12:26 -0600 Jonathan Corbet wrote:
> Bagas Sanjaya <bagasdotme@gmail.com> writes:
> >> It is a documentation patch, therefore not functionally touching
> >> code, maybe that could count as an exception?
> >
> > I think jon will pick up this patch, maybe as -rc-worthy fixes.
>
> The networking folks prefer to carry their own documentation patches,
> so I don't normally do that. I'd be happy to this time with a
> suitable ack.
>
> But honestly, there is nothing urgent about this change, I'd say just
> wait until net-next is open.
Sorry for the back and forth, the patch is waiting patchwork, we've
just been unusually busy the last two days. We'll apply it soon.
next prev parent reply other threads:[~2022-10-06 0:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-04 7:32 [PATCH net-next] docs: networking: phy: add missing space Casper Andersson
2022-10-04 10:30 ` Paolo Abeni
2022-10-04 18:35 ` Florian Fainelli
2022-10-05 9:38 ` Bagas Sanjaya
2022-10-05 14:12 ` Jonathan Corbet
2022-10-06 0:14 ` Jakub Kicinski [this message]
2022-10-05 7:21 ` Bagas Sanjaya
2022-10-06 4:00 ` patchwork-bot+netdevbpf
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=20221005171448.21c8c595@kernel.org \
--to=kuba@kernel.org \
--cc=andrew@lunn.ch \
--cc=bagasdotme@gmail.com \
--cc=casper.casan@gmail.com \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=f.fainelli@gmail.com \
--cc=hkallweit1@gmail.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--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;
as well as URLs for NNTP newsgroup(s).