public inbox for linux-staging@lists.linux.dev
 help / color / mirror / Atom feed
From: Dan Carpenter <dan.carpenter@linaro.org>
To: "M.samet Duman" <dumanmehmetsamet@icloud.com>
Cc: "Ö. Efe D." <skylinesytbe@gmail.com>,
	"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
	"Michael Straube" <straube.linux@gmail.com>,
	linux-staging@lists.linux.dev,
	"Ö. Efe D." <skyline@noreply.codeberg.org>,
	"Öner Efe Dasgüney" <efedasguney@protonmail.com>
Subject: Re: [PATCH] staging: rtl8723bs: fix whitespace issues in hal_com.c
Date: Mon, 2 Feb 2026 12:34:42 +0300	[thread overview]
Message-ID: <aYBvso52Z_-83lQW@stanley.mountain> (raw)
In-Reply-To: <96821010-58B3-49FD-865F-E9F420E4699A@icloud.com>

On Mon, Feb 02, 2026 at 10:08:02AM +0300, M.samet Duman wrote:
> Hello Ömer,
> 
> I wanted to share a brief observation regarding the patch titled:
> 
> “Remove spaces before tabs in comments to fix checkpatch warnings”
> 

That's not the title.  Why would you mention the title and then get it
wrong?  I'm so puzzled by this review.  Is it AI generated?  Please
only use AI if there are bugs, don't use AI to comment on the commit
message.

https://staticthinking.wordpress.com/2026/01/27/no-ai-slop/

Line wrap your emails at 72 characters?

regards,
dan carpenter


  reply	other threads:[~2026-02-02  9:34 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-02  2:18 [PATCH] staging: rtl8723bs: fix whitespace issues in hal_com.c Ö. Efe D.
2026-02-02  7:08 ` M.samet Duman
2026-02-02  9:34   ` Dan Carpenter [this message]
2026-02-02  9:49     ` Greg Kroah-Hartman
2026-02-02 11:39       ` Dan Carpenter
2026-02-02  9:38 ` Dan Carpenter
2026-02-07 13:18 ` Greg Kroah-Hartman

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=aYBvso52Z_-83lQW@stanley.mountain \
    --to=dan.carpenter@linaro.org \
    --cc=dumanmehmetsamet@icloud.com \
    --cc=efedasguney@protonmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-staging@lists.linux.dev \
    --cc=skyline@noreply.codeberg.org \
    --cc=skylinesytbe@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox