From: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
To: Alexander Duyck <alexander.duyck@gmail.com>,
Corentin Labbe <clabbe@baylibre.com>
Cc: Jonathan Corbet <corbet@lwn.net>,
intel-wired-lan <intel-wired-lan@lists.osuosl.org>,
linux-kernel@vger.kernel.org,
"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>
Subject: Re: [Intel-wired-lan] [PATCH] Documentation: networking: Update ixgb kconfig select documentation
Date: Tue, 06 Feb 2018 13:07:31 -0800 [thread overview]
Message-ID: <1517951251.9683.5.camel@intel.com> (raw)
In-Reply-To: <CAKgT0Uc-br8akeUyjf0FenLPLxDdq14D1rppjvb1yfNU33t+Mw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 915 bytes --]
On Tue, 2018-02-06 at 13:01 -0800, Alexander Duyck wrote:
> On Tue, Feb 6, 2018 at 12:42 PM, Corentin Labbe <clabbe@baylibre.com>
> wrote:
> > Update documentation on how to enable ixgb and ixgb DCB.
> > Simply remove NETDEV_10000 and replace it with the new used kconfig
> > names.
>
> Minor typo in the patch description. I assume you mean "ixgb and
> ixgbe
> DCB". Also you might want to mention ixgbe somewhere in the patch
> title.
>
> >
> > Signed-off-by: Corentin Labbe <clabbe@baylibre.com>
> > ---
> > Documentation/networking/ixgb.txt | 3 ++-
> > Documentation/networking/ixgbe.txt | 7 ++++---
> > 2 files changed, 6 insertions(+), 4 deletions(-)
I alredy have a patch to update the ixgbe kernel documentation, please
see the following patch:
http://patchwork.ozlabs.org/patch/870106/
With my updated documentation patch, the ixgbe hunk of your patch no
longer applies.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2018-02-06 21:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-06 20:42 [PATCH] Documentation: networking: Update ixgb kconfig select documentation Corentin Labbe
2018-02-06 21:01 ` [Intel-wired-lan] " Alexander Duyck
2018-02-06 21:07 ` Jeff Kirsher [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=1517951251.9683.5.camel@intel.com \
--to=jeffrey.t.kirsher@intel.com \
--cc=alexander.duyck@gmail.com \
--cc=clabbe@baylibre.com \
--cc=corbet@lwn.net \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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