mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "wanghai (M)" <wanghai38@huawei.com>
To: Jakub Kicinski <kuba@kernel.org>
Cc: <jeffrey.t.kirsher@intel.com>, <davem@davemloft.net>,
	<intel-wired-lan@lists.osuosl.org>, <netdev@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH net-next 0/3] Fix some kernel-doc warnings for e1000/e1000e
Date: Fri, 11 Sep 2020 09:42:23 +0800	[thread overview]
Message-ID: <53e857ff-f5c7-a2c9-b0ec-67c2d4ad29c3@huawei.com> (raw)
In-Reply-To: <20200910123819.3ce47422@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com>


在 2020/9/11 3:38, Jakub Kicinski 写道:
> On Thu, 10 Sep 2020 12:38:00 -0700 Jakub Kicinski wrote:
>> On Thu, 10 Sep 2020 23:04:26 +0800 Wang Hai wrote:
>>> Wang Hai (3):
>>>    e1000e: Fix some kernel-doc warnings in ich8lan.c
>>>    e1000e: Fix some kernel-doc warnings in netdev.c
>>>    e1000: Fix a bunch of kerneldoc parameter issues in e1000_hw.c
>> You should put some text here but I can confirm this set removes 17
>> warnings.
> Reviewed-by: Jakub Kicinski <kuba@kernel.org>
> .
Thans for your review, I'll add some description next time

      reply	other threads:[~2020-09-11  1:58 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-10 15:04 Wang Hai
2020-09-10 15:04 ` [PATCH net-next 1/3] e1000e: Fix some kernel-doc warnings in ich8lan.c Wang Hai
2020-09-10 15:04 ` [PATCH net-next 2/3] e1000e: Fix some kernel-doc warnings in netdev.c Wang Hai
2020-09-10 15:04 ` [PATCH net-next 3/3] e1000: Fix a bunch of kerneldoc parameter issues in e1000_hw.c Wang Hai
2020-09-10 19:38 ` [PATCH net-next 0/3] Fix some kernel-doc warnings for e1000/e1000e Jakub Kicinski
2020-09-10 19:38   ` Jakub Kicinski
2020-09-11  1:42     ` wanghai (M) [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=53e857ff-f5c7-a2c9-b0ec-67c2d4ad29c3@huawei.com \
    --to=wanghai38@huawei.com \
    --cc=davem@davemloft.net \
    --cc=intel-wired-lan@lists.osuosl.org \
    --cc=jeffrey.t.kirsher@intel.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@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

all inboxes | Powered by JetHome®