All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Bramwel Barack <bramwelbarack89@gmail.com>
Cc: linux-staging@lists.linux.dev
Subject: Re: [PATCH v2] staging: rtl8723bs: fix line length warnings in os_intfs.c
Date: Wed, 29 Jul 2026 11:13:02 +0200	[thread overview]
Message-ID: <2026072924-daunting-footing-189d@gregkh> (raw)
In-Reply-To: <amm_xjWhiP50C5lG@fedora>

On Wed, Jul 29, 2026 at 11:54:30AM +0300, Bramwel Barack wrote:
> Hi Greg,
> 
> This is a v2 patch addressing your feedback on comment block placement
> and providing the missing commit description text.

As per the documentation, the v2 stuff goes below the --- line, right?

Take a look at the mailing list for hundreds of examples to follow.
This style here will not work well.

> 
> Thanks,
> Bramwel
> 
> ---
> 
> >From 8fb05fdee4c523bcafc5b425851b95e69e22182a Mon Sep 17 00:00:00 2001
> From: Bramwel Barack <bramwelbarack89@gmail.com>
> Date: Wed, 29 Jul 2026 09:33:57 +0300
> Subject: [PATCH v2] staging: rtl8723bs: fix line length warnings in os_intfs.c
> 
> Fix coding style warnings where comment lines exceeded the 100-character limit. Move the split multi-line comment block above the target variable declaration to comply with standard kernel comment formatting.

The irony of a line length warning patch having a line-length issue in
the changelog text itself is quite high :)

Always run checkpatch.pl on your changes before sending them out.
Again, look at the tool 'b4', it has an option to run checkpatch on the
patch before it is sent out.

thanks,

greg k-h

  reply	other threads:[~2026-07-29  9:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-29  8:54 [PATCH v2] staging: rtl8723bs: fix line length warnings in os_intfs.c Bramwel Barack
2026-07-29  9:13 ` Greg KH [this message]
2026-07-29  9:31 ` Dan Carpenter

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=2026072924-daunting-footing-189d@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=bramwelbarack89@gmail.com \
    --cc=linux-staging@lists.linux.dev \
    /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.