From: David Miller <davem@davemloft.net>
To: eric@engestrom.ch
Cc: linux-kernel@vger.kernel.org, corbet@lwn.net,
dsa@cumulusnetworks.com, shm@cumulusnetworks.com,
brouer@redhat.com, ast@plumgrid.com, linux-doc@vger.kernel.org,
netdev@vger.kernel.org
Subject: Re: [PATCH 30/41] Documentation: networking: fix spelling mistakes
Date: Thu, 28 Apr 2016 14:21:22 -0400 (EDT) [thread overview]
Message-ID: <20160428.142122.120683880587946479.davem@davemloft.net> (raw)
In-Reply-To: <1461566229-4717-4-git-send-email-eric@engestrom.ch>
From: Eric Engestrom <eric@engestrom.ch>
Date: Mon, 25 Apr 2016 07:36:56 +0100
> Signed-off-by: Eric Engestrom <eric@engestrom.ch>
Applied.
prev parent reply other threads:[~2016-04-28 18:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1461543878-3639-1-git-send-email-eric@engestrom.ch>
[not found] ` <1461566229-4717-1-git-send-email-eric@engestrom.ch>
2016-04-25 6:36 ` [PATCH 30/41] Documentation: networking: fix spelling mistakes Eric Engestrom
2016-04-28 18:21 ` David Miller [this message]
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=20160428.142122.120683880587946479.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=ast@plumgrid.com \
--cc=brouer@redhat.com \
--cc=corbet@lwn.net \
--cc=dsa@cumulusnetworks.com \
--cc=eric@engestrom.ch \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=shm@cumulusnetworks.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).