From: Jesse Brandeburg <jesse.brandeburg@intel.com>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] [PATCH net-next 0/3] Fix some kernel-doc warnings for i40e
Date: Thu, 10 Sep 2020 17:49:26 -0700 [thread overview]
Message-ID: <20200910174926.00004f0e@intel.com> (raw)
In-Reply-To: <20200910150934.34605-1-wanghai38@huawei.com>
Wang Hai wrote:
> Wang Hai (3):
> i40e: Fix some kernel-doc warnings in i40e_client.c
> i40e: Fix some kernel-doc warnings in i40e_common.c
> i40e: Fix a kernel-doc warning in i40e_ptp.c
>
> drivers/net/ethernet/intel/i40e/i40e_client.c | 2 --
> drivers/net/ethernet/intel/i40e/i40e_common.c | 2 --
> drivers/net/ethernet/intel/i40e/i40e_ptp.c | 1 -
> 3 files changed, 5 deletions(-)
>
Please see my patchset [1]: I've already fixed all of these and many
others.
In fact, before you continue, I have a whole set done making the entire
drivers/net/ethernet directory compile cleanly with W=1, that I'm about
to send, but they depend on [1]
[1]
https://patchwork.ozlabs.org/project/intel-wired-lan/list/?series=&submitter=189&state=&q=&archive=&delegate=
WARNING: multiple messages have this Message-ID (diff)
From: Jesse Brandeburg <jesse.brandeburg@intel.com>
To: Wang Hai <wanghai38@huawei.com>
Cc: <jeffrey.t.kirsher@intel.com>, <davem@davemloft.net>,
<kuba@kernel.org>, <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 i40e
Date: Thu, 10 Sep 2020 17:49:26 -0700 [thread overview]
Message-ID: <20200910174926.00004f0e@intel.com> (raw)
In-Reply-To: <20200910150934.34605-1-wanghai38@huawei.com>
Wang Hai wrote:
> Wang Hai (3):
> i40e: Fix some kernel-doc warnings in i40e_client.c
> i40e: Fix some kernel-doc warnings in i40e_common.c
> i40e: Fix a kernel-doc warning in i40e_ptp.c
>
> drivers/net/ethernet/intel/i40e/i40e_client.c | 2 --
> drivers/net/ethernet/intel/i40e/i40e_common.c | 2 --
> drivers/net/ethernet/intel/i40e/i40e_ptp.c | 1 -
> 3 files changed, 5 deletions(-)
>
Please see my patchset [1]: I've already fixed all of these and many
others.
In fact, before you continue, I have a whole set done making the entire
drivers/net/ethernet directory compile cleanly with W=1, that I'm about
to send, but they depend on [1]
[1]
https://patchwork.ozlabs.org/project/intel-wired-lan/list/?series=&submitter=189&state=&q=&archive=&delegate=
next prev parent reply other threads:[~2020-09-11 0:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-10 15:09 [Intel-wired-lan] [PATCH net-next 0/3] Fix some kernel-doc warnings for i40e Wang Hai
2020-09-10 15:09 ` Wang Hai
2020-09-10 15:09 ` [Intel-wired-lan] [PATCH net-next 1/3] i40e: Fix some kernel-doc warnings in i40e_client.c Wang Hai
2020-09-10 15:09 ` Wang Hai
2020-09-10 15:09 ` [Intel-wired-lan] [PATCH net-next 2/3] i40e: Fix some kernel-doc warnings in i40e_common.c Wang Hai
2020-09-10 15:09 ` Wang Hai
2020-09-10 15:09 ` [Intel-wired-lan] [PATCH net-next 3/3] i40e: Fix a kernel-doc warning in i40e_ptp.c Wang Hai
2020-09-10 15:09 ` Wang Hai
2020-09-11 0:49 ` Jesse Brandeburg [this message]
2020-09-11 0:49 ` [PATCH net-next 0/3] Fix some kernel-doc warnings for i40e Jesse Brandeburg
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=20200910174926.00004f0e@intel.com \
--to=jesse.brandeburg@intel.com \
--cc=intel-wired-lan@osuosl.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.