From: Luka Gejak <luka.gejak@linux.dev>
To: Akhil <boyakhil978@gmail.com>
Cc: gregkh@linuxfoundation.org, linux-staging@lists.linux.dev,
linux-kernel@vger.kernel.org, luka.gejak@linux.dev
Subject: Re: [PATCH RESEND] staging: rtl8723bs: fix comparison to false
Date: Fri, 10 Apr 2026 08:16:10 +0200 [thread overview]
Message-ID: <4E4059A8-7327-4901-AA08-D318BE40BC5B@linux.dev> (raw)
In-Reply-To: <adgYE4va2Eg3V4HG@Akhil>
On April 9, 2026 11:20:19 PM GMT+02:00, Akhil <boyakhil978@gmail.com> wrote:
>On Thu, Apr 09, 2026 at 03:41:06PM +0200, Luka Gejak wrote:
>> Hi Akhil,
>> I am also wondering why did you decide to resend the patch as it
>> impplies it was sent somewhere else, but I don't see it anywhere on
>> mailing list. Did you send it only to Greg?
>Yes, I accidentally only sent it to Greg, I realised this and resent it
>before I could get the response from Greg's bot. The content of the
>patch is exactly the same.
>
>It took me some time for this reply as I was understanding the correct method to reply, let me know if anything can be improved.
This should be resent as v2, because I'm sure you didn't include
"RESEND adding cc to linux-staging@lists.linux.dev" in original email.
You should only use RESEND if you don't edit context of email at all.
Also such messages for changes (as "RESEND adding cc to
linux-staging@lists.linux.dev") should go under --- as everything
above is part of the commit message.
prev parent reply other threads:[~2026-04-10 6:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-08 17:38 [PATCH RESEND] staging: rtl8723bs: fix comparison to false Akhil Boyapati
2026-04-09 13:41 ` Luka Gejak
2026-04-09 21:20 ` Akhil
2026-04-10 6:16 ` Luka Gejak [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=4E4059A8-7327-4901-AA08-D318BE40BC5B@linux.dev \
--to=luka.gejak@linux.dev \
--cc=boyakhil978@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox