From: Jesse Brandeburg <jesse.brandeburg@intel.com>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] [RFC PATCH net-next v1 10/11] drivers/net/ethernet: remove incorrectly formatted doc
Date: Fri, 11 Sep 2020 16:25:57 -0700 [thread overview]
Message-ID: <20200911162557.000002d2@intel.com> (raw)
In-Reply-To: <fbd1fdd9-1000-8aac-7e5c-bc761b2209e1@intel.com>
Jacob Keller wrote:
> A lot of these look like they should probably just be converted to use
> kdoc format instead of removing the '/**'
I understand why you're saying that, and I spent a considerable amount
of time fixing drivers that appeared to *try* to use kdoc but messed
up. However, if they don't have anything that looks like doxygen or
kdoc, then I just removed the "/**" to a /* and stopped kdoc processing.
The temac driver is a good example of not actually trying to kdoc at
all.
However I will look over the patches and see if I see @brief anywhere
that is left and try to fix those up. I've done so much now I might as
well finish it, but the @brief doxygen style notes had never been
processed into kdoc before, so changing the /** into /* doesn't
actually remove any value, just makes the build clean.
> > diff --git a/drivers/net/ethernet/aquantia/atlantic/hw_atl/hw_atl_b0.c b/drivers/net/ethernet/aquantia/atlantic/hw_atl/hw_atl_b0.c
> > index 8941ac4df9e3..9f1b15077e7d 100644
> > --- a/drivers/net/ethernet/aquantia/atlantic/hw_atl/hw_atl_b0.c
> > +++ b/drivers/net/ethernet/aquantia/atlantic/hw_atl/hw_atl_b0.c
> > @@ -1536,7 +1536,7 @@ static int hw_atl_b0_hw_fl2_clear(struct aq_hw_s *self,
> > return aq_hw_err_from_flags(self);
> > }
> >
> > -/**
> > +/*
> > * @brief Set VLAN filter table
> > * @details Configure VLAN filter table to accept (and assign the queue) traffic
> > * for the particular vlan ids.
>
> This looks like a doxygen style comment. I wonder if whoever maintains
> this code uses doxygen and expects this to get picked up.
It was never picked up by kdoc. And in this case this is the only kdoc
comment in this whole file, so I didn't like the idea of this *one*
being documented while the whole rest of the driver was not.
> > diff --git a/drivers/net/ethernet/xilinx/ll_temac_main.c b/drivers/net/ethernet/xilinx/ll_temac_main.c
> > index 9a15f14daa47..60c199fcb91e 100644
> > --- a/drivers/net/ethernet/xilinx/ll_temac_main.c
> > +++ b/drivers/net/ethernet/xilinx/ll_temac_main.c
> > @@ -106,7 +106,7 @@ static bool hard_acs_rdy_or_timeout(struct temac_local *lp, ktime_t timeout)
> > */
> > #define HARD_ACS_RDY_POLL_NS (20 * NSEC_PER_MSEC)
> >
> > -/**
> > +/*
> > * temac_indirect_busywait - Wait for current indirect register access
> > * to complete.
> > */
>
> This looks like a function comment. Shouldn't this just be fixed/updated
> so that it is a valid kdoc comment instead?
As per above, this driver didn't even try to use kdoc, so I just
honored their original intent and removed /**.
Thanks for the review and comments!
next prev parent reply other threads:[~2020-09-11 23:25 UTC|newest]
Thread overview: 68+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-11 1:23 [Intel-wired-lan] [RFC PATCH net-next v1 00/11] make drivers/net/ethernet W=1 clean Jesse Brandeburg
2020-09-11 1:23 ` Jesse Brandeburg
2020-09-11 1:23 ` [Intel-wired-lan] [RFC PATCH net-next v1 01/11] i40e: prepare flash string in a simpler way Jesse Brandeburg
2020-09-11 1:23 ` Jesse Brandeburg
2020-09-11 1:23 ` [Intel-wired-lan] [RFC PATCH net-next v1 02/11] i40e: clean up W=1 warnings in i40e Jesse Brandeburg
2020-09-11 1:23 ` Jesse Brandeburg
2020-09-23 2:02 ` [Intel-wired-lan] " Brown, Aaron F
2020-09-23 2:02 ` Brown, Aaron F
2020-09-11 1:23 ` [Intel-wired-lan] [RFC PATCH net-next v1 03/11] iavf: clean up W=1 warnings in iavf Jesse Brandeburg
2020-09-11 1:23 ` Jesse Brandeburg
2020-09-23 3:12 ` [Intel-wired-lan] " Brown, Aaron F
2020-09-11 1:23 ` [Intel-wired-lan] [RFC PATCH net-next v1 04/11] ixgbe: clean up W=1 warnings in ixgbe Jesse Brandeburg
2020-09-11 1:23 ` Jesse Brandeburg
2020-09-23 3:57 ` [Intel-wired-lan] " Brown, Aaron F
2020-09-11 1:23 ` [Intel-wired-lan] [RFC PATCH net-next v1 05/11] intel-ethernet: make W=1 build cleanly Jesse Brandeburg
2020-09-11 1:23 ` Jesse Brandeburg
2020-09-11 17:43 ` [Intel-wired-lan] " Vinicius Costa Gomes
2020-09-11 17:43 ` Vinicius Costa Gomes
2020-09-11 23:06 ` Jacob Keller
2020-09-11 23:28 ` Jesse Brandeburg
2020-09-11 23:28 ` Jesse Brandeburg
2020-09-11 1:23 ` [Intel-wired-lan] [RFC PATCH net-next v1 06/11] drivers/net/ethernet: clean up unused assignments Jesse Brandeburg
2020-09-11 1:23 ` Jesse Brandeburg
2020-09-11 17:16 ` [Intel-wired-lan] " Edward Cree
2020-09-11 17:16 ` Edward Cree
2020-09-11 23:03 ` [Intel-wired-lan] " Jacob Keller
2020-09-11 23:18 ` Jesse Brandeburg
2020-09-11 1:23 ` [Intel-wired-lan] [RFC PATCH net-next v1 07/11] drivers/net/ethernet: rid ethernet of no-prototype warnings Jesse Brandeburg
2020-09-11 1:23 ` Jesse Brandeburg
2020-09-11 1:23 ` [Intel-wired-lan] [RFC PATCH net-next v1 08/11] drivers/net/ethernet: handle one warning explicitly Jesse Brandeburg
2020-09-11 1:23 ` Jesse Brandeburg
2020-09-11 22:56 ` [Intel-wired-lan] " Jacob Keller
2020-09-11 22:56 ` Jacob Keller
2020-09-11 1:23 ` [Intel-wired-lan] [RFC PATCH net-next v1 09/11] drivers/net/ethernet: add some basic kdoc tags Jesse Brandeburg
2020-09-11 1:23 ` Jesse Brandeburg
2020-09-11 1:23 ` [Intel-wired-lan] [RFC PATCH net-next v1 10/11] drivers/net/ethernet: remove incorrectly formatted doc Jesse Brandeburg
2020-09-11 1:23 ` Jesse Brandeburg
2020-09-11 22:59 ` [Intel-wired-lan] " Jacob Keller
2020-09-11 23:25 ` Jesse Brandeburg [this message]
2020-09-14 23:06 ` Jacob Keller
2020-09-11 1:23 ` [Intel-wired-lan] [RFC PATCH net-next v1 11/11] drivers/net/ethernet: clean up mis-targeted comments Jesse Brandeburg
2020-09-11 1:23 ` Jesse Brandeburg
2020-09-11 17:26 ` [Intel-wired-lan] " Edward Cree
2020-09-11 17:26 ` Edward Cree
2020-09-11 21:42 ` [Intel-wired-lan] " Jesse Brandeburg
2020-09-11 21:42 ` Jesse Brandeburg
2020-09-11 21:55 ` [Intel-wired-lan] " Edward Cree
2020-09-11 21:55 ` Edward Cree
2020-09-11 22:26 ` [Intel-wired-lan] " Jakub Kicinski
2020-09-11 22:26 ` Jakub Kicinski
2020-09-11 23:11 ` [Intel-wired-lan] " Edward Cree
2020-09-11 23:11 ` Edward Cree
2020-09-12 0:49 ` [Intel-wired-lan] " Jesse Brandeburg
2020-09-12 0:49 ` Jesse Brandeburg
2020-09-14 3:04 ` [Intel-wired-lan] " Andrew Lunn
2020-09-14 3:04 ` Andrew Lunn
2020-09-11 14:55 ` [Intel-wired-lan] [RFC PATCH net-next v1 00/11] make drivers/net/ethernet W=1 clean Jakub Kicinski
2020-09-11 14:55 ` Jakub Kicinski
2020-09-11 19:00 ` [Intel-wired-lan] " Jesse Brandeburg
2020-09-11 19:00 ` Jesse Brandeburg
2020-09-11 20:12 ` [Intel-wired-lan] " Jakub Kicinski
2020-09-11 20:12 ` Jakub Kicinski
2020-09-11 21:34 ` [Intel-wired-lan] " Jesse Brandeburg
2020-09-11 21:34 ` Jesse Brandeburg
2020-09-11 22:16 ` [Intel-wired-lan] " Jakub Kicinski
2020-09-11 22:16 ` Jakub Kicinski
2020-09-11 22:43 ` [Intel-wired-lan] " Vladimir Oltean
2020-09-11 22:43 ` Vladimir Oltean
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=20200911162557.000002d2@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.