From: Bagas Sanjaya <bagasdotme@gmail.com>
To: 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>,
Jakub Kicinski <kuba@kernel.org>,
Jonathan Corbet <corbet@lwn.net>,
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 16:38:00 +0700 [thread overview]
Message-ID: <30e3cee2-420b-b2bc-9af0-9f7e9c696c57@gmail.com> (raw)
In-Reply-To: <a495dd76-060a-210a-1a11-55333d67180c@gmail.com>
On 10/5/22 01:35, Florian Fainelli wrote:
> On 10/4/22 03:30, Paolo Abeni wrote:
>> On Tue, 2022-10-04 at 09:32 +0200, Casper Andersson wrote:
>>> Missing space between "pins'" and "strength"
>>>
>>> Signed-off-by: Casper Andersson <casper.casan@gmail.com>
>>> ---
>>
>> The merge window has now started (after Linus tagged 6.0)
>> and will last until he tags 6.1-rc1 (two weeks from now). During this
>> time we'll not be taking any patches for net-next so
>> please repost in around 2 weeks.
>
> 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.
--
An old man doll... just what I always wanted! - Clara
next prev parent reply other threads:[~2022-10-05 9:38 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 [this message]
2022-10-05 14:12 ` Jonathan Corbet
2022-10-06 0:14 ` Jakub Kicinski
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=30e3cee2-420b-b2bc-9af0-9f7e9c696c57@gmail.com \
--to=bagasdotme@gmail.com \
--cc=andrew@lunn.ch \
--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=kuba@kernel.org \
--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).