public inbox for linux-staging@lists.linux.dev
 help / color / mirror / Atom feed
From: "Salman Alghamdi" <me@cipherat.com>
To: "Dan Carpenter" <error27@gmail.com>
Cc: gregkh@linuxfoundation.org, luka.gejak@linux.dev,
	straube.linux@gmail.com, linux-staging@lists.linux.dev,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 2/5] staging: rtl8723bs: rtw_mlme: fix lines exceeding 100  columns
Date: Mon, 27 Apr 2026 18:46:34 +0300	[thread overview]
Message-ID: <5d82ba44-eba0-0d0d-4cdf-fe58a3e6cb75@cipherat.com> (raw)
In-Reply-To: <ae8oIMM08ntVQFdO@stanley.mountain>

On April 27, 2026 12:10 +03, Dan Carpenter <error27@gmail.com> wrote:

> This patch is too big and too complicated.  If you send a patch that
> only adds newlines, then I have automated ways to review that but
> when you're adding variables and change code to use min_t() then
> it's hard to review.

The introduction of some variables was made in order to fix line
length for certain function calls that has long named parameters.
Should I separate long line fixes into two patches, one only for
simple newlines and the other that introduces variables?

> When you start doing things which are more complicated than
> just adding newlines, then it gets controversial in ways you
> don't expect.  For example, we don't really use min_t() these
> days.

I tried using min() first as Luka noted me, but checkpatch.pl warned
to replace it with min_t() instead. What is the preferred function
to use in this case?

Regards,
Salman Alghamdi


  reply	other threads:[~2026-04-27 15:46 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 [this message]
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

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=5d82ba44-eba0-0d0d-4cdf-fe58a3e6cb75@cipherat.com \
    --to=me@cipherat.com \
    --cc=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=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox