netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: tparkin@katalix.com
Cc: netdev@vger.kernel.org, jchapman@katalix.com
Subject: Re: [PATCH v2 net-next 00/10] l2tp: cleanup checkpatch.pl warnings
Date: Wed, 22 Jul 2020 18:08:55 -0700 (PDT)	[thread overview]
Message-ID: <20200722.180855.1247228846076080749.davem@davemloft.net> (raw)
In-Reply-To: <20200722163214.7920-1-tparkin@katalix.com>

From: Tom Parkin <tparkin@katalix.com>
Date: Wed, 22 Jul 2020 17:32:04 +0100

> l2tp hasn't been kept up to date with the static analysis checks offered
> by checkpatch.pl.
> 
> This series addresses a range of minor issues which don't involve large
> changes to code structure.  The changes include:
> 
>  * tweaks to use of whitespace, comment style, line breaks,
>    and indentation
> 
>  * two minor modifications to code to use a function or macro suggested
>    by checkpatch
> 
> v1 -> v2
> 
>  * combine related patches (patches fixing whitespace issues, patches
>    addressing comment style)
> 
>  * respin the single large patchset into a multiple smaller series for
>    easier review

Series applied, thank you.

      parent reply	other threads:[~2020-07-23  1:08 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-22 16:32 [PATCH v2 net-next 00/10] l2tp: cleanup checkpatch.pl warnings Tom Parkin
2020-07-22 16:32 ` [PATCH 01/10] l2tp: cleanup whitespace use Tom Parkin
2020-07-22 16:32 ` [PATCH 02/10] l2tp: cleanup comments Tom Parkin
2020-07-22 16:32 ` [PATCH 03/10] l2tp: cleanup difficult-to-read line breaks Tom Parkin
2020-07-22 16:32 ` [PATCH 04/10] l2tp: cleanup wonky alignment of line-broken function calls Tom Parkin
2020-07-22 16:32 ` [PATCH 05/10] l2tp: cleanup suspect code indent Tom Parkin
2020-07-22 16:32 ` [PATCH 06/10] l2tp: add identifier name in function pointer prototype Tom Parkin
2020-07-22 16:32 ` [PATCH 07/10] l2tp: prefer using BIT macro Tom Parkin
2020-07-22 16:32 ` [PATCH 08/10] l2tp: prefer seq_puts for unformatted output Tom Parkin
2020-07-22 16:32 ` [PATCH 09/10] l2tp: line-break long function prototypes Tom Parkin
2020-07-22 16:32 ` [PATCH 10/10] l2tp: avoid precidence issues in L2TP_SKB_CB macro Tom Parkin
2020-07-22 18:31 ` [PATCH v2 net-next 00/10] l2tp: cleanup checkpatch.pl warnings James Chapman
2020-07-23  1:08 ` David Miller [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=20200722.180855.1247228846076080749.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=jchapman@katalix.com \
    --cc=netdev@vger.kernel.org \
    --cc=tparkin@katalix.com \
    /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).