From: Pavel Machek <pavel@ucw.cz>
To: Jonathan Corbet <corbet@lwn.net>,
davem@davemloft.net, netdev@vger.kernel.org
Cc: "Darrick J. Wong" <darrick.wong@oracle.com>,
linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org,
tytso@mit.edu, linux-ext4@vger.kernel.org,
Andrew Morton <akpm@osdl.org>
Subject: Re: [PATCH] Documentation: fix little inconsistencies
Date: Tue, 29 Aug 2017 22:34:11 +0200 [thread overview]
Message-ID: <20170829203411.GA21650@amd> (raw)
In-Reply-To: <20170829130945.7603d035@lwn.net>
[-- Attachment #1: Type: text/plain, Size: 2531 bytes --]
On Tue 2017-08-29 13:09:45, Jonathan Corbet wrote:
> On Tue, 29 Aug 2017 09:50:57 -0700
> "Darrick J. Wong" <darrick.wong@oracle.com> wrote:
>
> > > Anything wrong here? It is fixing extra '+' in the ascii art...
> >
> > There's nothing incorrect here, I merely thought it odd to send a fix
> > for networking documentation to the ext4 list, but not netdev?
>
> In fact, davem likes to handle networking documentation patches himself,
> so resending this one to netdev would be a good idea.
Its a typo in documentation, do we really need to waste any more time
with it? Dave, can you just ack it?
> > index 5e40e1f..6309e90 100644
> > --- a/Documentation/networking/switchdev.txt
> > +++ b/Documentation/networking/switchdev.txt
> > @@ -29,7 +29,7 @@ with SR-IOV or soft switches, such as OVS, are
> > possible.
> > sw1p1 + sw1p3 + sw1p5 + eth1
> > + | + | + | +
> > | | | | | | |
> > - +--+----+----+----+-+--+----+---+ +-----+-----+
> > + +--+----+----+----+----+----+---+ +-----+-----+
Besides, if documentation fixes should go to Davem/netdev,
getmaintainer.pl should say so:
pavel@duo:/data/l/linux-n900$ scripts/get_maintainer.pl -f
Documentation/networking
Jonathan Corbet <corbet@lwn.net> (maintainer:DOCUMENTATION)
"David S. Miller" <davem@davemloft.net> (commit_signer:52/87=60%)
David Howells <dhowells@redhat.com>
(commit_signer:7/87=8%,authored:8/87=9%)
Florian Fainelli <f.fainelli@gmail.com> (commit_signer:6/87=7%)
Mauro Carvalho Chehab <mchehab@kernel.org>
(commit_signer:6/87=7%,authored:5/87=6%)
Yuchung Cheng <ycheng@google.com> (commit_signer:6/87=7%)
Hangbin Liu <liuhangbin@gmail.com> (authored:5/87=6%)
linux-doc@vger.kernel.org (open list:DOCUMENTATION)
linux-kernel@vger.kernel.org (open list)
pavel@duo:/data/l/linux-n900$
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
next prev parent reply other threads:[~2017-08-29 20:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-28 9:46 [PATCH] Documentation: fix little inconsistencies Pavel Machek
2017-08-28 16:17 ` Darrick J. Wong
2017-08-29 7:27 ` Pavel Machek
2017-08-29 16:50 ` Darrick J. Wong
2017-08-29 19:09 ` Jonathan Corbet
2017-08-29 20:34 ` Pavel Machek [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-09-16 11:48 Pavel Machek
2017-09-26 20:30 ` Jonathan Corbet
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=20170829203411.GA21650@amd \
--to=pavel@ucw.cz \
--cc=akpm@osdl.org \
--cc=corbet@lwn.net \
--cc=darrick.wong@oracle.com \
--cc=davem@davemloft.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=tytso@mit.edu \
/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).