netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Poirier <benjamin.poirier@gmail.com>
To: Jarrett Knauer <jrtknauer@gmail.com>
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH] staging: qlge: Fixed extra indentation in qlget_get_stats()
Date: Tue, 11 Feb 2020 15:50:01 +0900	[thread overview]
Message-ID: <20200211065001.GA5718@f3> (raw)
In-Reply-To: <45451eb8-e6a9-2e7a-e2fd-680b31e38717@gmail.com>

On 2020/02/10 11:31 -0700, Jarrett Knauer wrote:
> On 2020-02-09 9:31 p.m., Benjamin Poirier wrote:
> > On 2020/02/09 00:36 -0700, Jarrett Knauer wrote:
> >> qlge TODO cited weird indentation all over qlge files, with
> >> qlget_get_stats() as an example. With this fix the TODO will need to be
> >> updated as well.
> >>
> >> This is also a re-submission, as I incorrectly sent my first patch
> >> directly to the maintainers instead of to the correct mailing list.
> >> Apologies.
> > If you really want to fix this, I would suggest to go over all of the
> > driver at once. Then you can remove the TODO entry.
> I can do this. Would it be best for me to re-submit this patch in a series of patches with each indentation fix that I go through + a cover letter for the series?

A quick run of `clang-format` shows:
5 files changed, 2305 insertions(+), 2407 deletions(-)
Many of those are unneeded but I guess it will still be a lot of changes.

There is not much benefit to splitting each small indentation fix into
separate patches: it doesn't help to understand the patch, it doesn't
help bisectability, it's debatable that they are logically distinct
changes.

If you want, you could split them into topics like "fix code formatting
in enum/struct definitions/function bodies/preprocessor directives/...
Then again, if the overall changes turn out not to be that large, a
single patch would be fine I think.

Please make sure to read Documentation/process/coding-style.rst; that
doesn't go into every small detail and some things are up to the
preference of whoever wrote the code. In case of doubt, I'd suggest to
look at other drivers in drivers/net/ethernet/ that are not too old:
ice, ionic, sfc, mlx5, ...

      reply	other threads:[~2020-02-11  6:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-09  7:36 [PATCH] staging: qlge: Fixed extra indentation in qlget_get_stats() Jarrett Knauer
2020-02-10  4:31 ` Benjamin Poirier
2020-02-10 18:31   ` Jarrett Knauer
2020-02-11  6:50     ` Benjamin Poirier [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=20200211065001.GA5718@f3 \
    --to=benjamin.poirier@gmail.com \
    --cc=jrtknauer@gmail.com \
    --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;
as well as URLs for NNTP newsgroup(s).