Linux IIO development
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: William Breathitt Gray <william.gray@linaro.org>
Cc: linux-iio@vger.kernel.org, Yanteng Si <siyanteng@loongson.cn>
Subject: Re: [PATCH 2/2] counter: Realign counter_comp comment block to 80 characters
Date: Thu, 22 Sep 2022 13:28:15 +0200	[thread overview]
Message-ID: <YyxGz77qKgDo/rOu@kroah.com> (raw)
In-Reply-To: <8294b04153c33602e9c3dd21ac90c1e99bd0fdaf.1663844776.git.william.gray@linaro.org>

On Thu, Sep 22, 2022 at 07:20:57AM -0400, William Breathitt Gray wrote:
> The member documentation comment lines for struct counter_comp extend
> past the 80-characters column boundary due to extra identation at the
> start of each section. This patch realigns the comment block within the
> 80-characters boundary by removing these superfluous indents.
> 
> Reviewed-by: Yanteng Si <siyanteng@loongson.cn>
> Link: https://lore.kernel.org/r/20220902120839.4260-1-william.gray@linaro.org/
> Signed-off-by: William Breathitt Gray <william.gray@linaro.org>
> ---
>  include/linux/counter.h | 40 ++++++++++++++++++++--------------------
>  1 file changed, 20 insertions(+), 20 deletions(-)

This isn't needed for 6.0-final, I'll queue it up in my -next branch for
6.1-rc1.

thanks,

greg k-h

      reply	other threads:[~2022-09-22 11:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-22 11:20 [PATCH 0/2] First set of Counter fixes for 6.0 William Breathitt Gray
2022-09-22 11:20 ` [PATCH 1/2] counter: 104-quad-8: Fix skipped IRQ lines during events configuration William Breathitt Gray
2022-09-22 11:27   ` Greg KH
2022-09-22 11:20 ` [PATCH 2/2] counter: Realign counter_comp comment block to 80 characters William Breathitt Gray
2022-09-22 11:28   ` Greg KH [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=YyxGz77qKgDo/rOu@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=linux-iio@vger.kernel.org \
    --cc=siyanteng@loongson.cn \
    --cc=william.gray@linaro.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