All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dan Carpenter <error27@gmail.com>
To: Luka Gejak <luka.gejak@linux.dev>
Cc: Salman Alghamdi <me@cipherat.com>,
	gregkh@linuxfoundation.org, straube.linux@gmail.com,
	linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 0/5] staging: rtl8723bs: rtw_mlme: fix long lines and related issues
Date: Mon, 27 Apr 2026 12:01:50 +0300	[thread overview]
Message-ID: <ae8l_lfT-BH81TWQ@stanley.mountain> (raw)
In-Reply-To: <DI3PQIL60XS9.3S9DP1GE4I8P2@linux.dev>

On Mon, Apr 27, 2026 at 08:11:27AM +0200, Luka Gejak wrote:
> On Mon Apr 27, 2026 at 1:12 AM CEST, Salman Alghamdi wrote:
> > I noticed the function signature continuation lines appear misaligned
> > in the mailing list archive. I've verified the alignment in the file
> > using cat -A which shows correct tabs+spaces:
> >
> >   ^I^I^I^I^I    struct wlan_network *network)
> >
> > The misalignment appears to be a rendering artifact in the email
> > client or archive. If you can verify by applying the patch locally
> > I'd appreciate confirmation, or if there's a known fix I'm happy
> > to address it.
> >
> > Regards,
> > Salman Alghamdi.
> 
> I am confused in email it's misaligned but when I apply and check file 
> it's looking good. Anyone knows why?

It's because in a diff every line starts with an extra [ +-] char.

regards,
dan carpenter


      reply	other threads:[~2026-04-27  9:01 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-26 22:54 [PATCH v3 0/5] staging: rtl8723bs: rtw_mlme: fix long lines and related issues Salman Alghamdi
2026-04-26 22:54 ` [PATCH v3 1/5] staging: rtl8723bs: fix buffer over-read in rtw_update_protection Salman Alghamdi
2026-04-26 22:54 ` [PATCH v3 2/5] staging: rtl8723bs: rtw_mlme: fix lines exceeding 100 columns Salman Alghamdi
2026-04-27  5:50   ` Luka Gejak
2026-04-27  6:22     ` Luka Gejak
2026-04-27  6:02   ` Luka Gejak
2026-04-27  9:10   ` Dan Carpenter
2026-04-27 15:46     ` Salman Alghamdi
2026-04-27 16:02       ` Luka Gejak
2026-04-26 22:55 ` [PATCH v3 3/5] staging: rtl8723bs: rtw_mlme: remove dead commented-out code Salman Alghamdi
2026-04-27  5:32   ` Luka Gejak
2026-04-26 22:55 ` [PATCH v3 4/5] staging: rtl8723bs: rtw_mlme: consolidate capability comparisons lines Salman Alghamdi
2026-04-26 22:55 ` [PATCH v3 5/5] staging: rtl8723bs: rtw_mlme: add blank line for readability Salman Alghamdi
2026-04-26 23:12 ` [PATCH v3 0/5] staging: rtl8723bs: rtw_mlme: fix long lines and related issues Salman Alghamdi
2026-04-27  6:11   ` Luka Gejak
2026-04-27  9:01     ` Dan Carpenter [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=ae8l_lfT-BH81TWQ@stanley.mountain \
    --to=error27@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-staging@lists.linux.dev \
    --cc=luka.gejak@linux.dev \
    --cc=me@cipherat.com \
    --cc=straube.linux@gmail.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 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.