All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Moksh Panicker <mokshpanicker.7@gmail.com>
Cc: linux-staging@lists.linux.dev
Subject: Re: [PATCH 1/4] staging: rtl8723bs: reformat rtw_efuse_read_1_byte() signature
Date: Fri, 15 May 2026 14:33:25 +0200	[thread overview]
Message-ID: <2026051503-crudely-mossy-19f9@gregkh> (raw)
In-Reply-To: <CAK0z5OmSunDp2xVhwEcy+gYz7KCXPihSV3R4zLn-ia39Lbtirg@mail.gmail.com>

On Fri, May 15, 2026 at 05:37:24PM +0530, Moksh Panicker wrote:
> Apologies for the confusion. I sent a v1 series earlier and then
> resent as v2, both ended up on the list. The [PATCH 1/4] subject
> was a mistake on my part; this is actually a 3-patch series with
> no cover letter. I'll make sure to number them correctly and
> include a cover letter in future submissions.
> 
> Should I resend the series as v3 with the correct numbering
> ([PATCH 1/3], [PATCH 2/3], [PATCH 3/3]) and a [PATCH 0/3](PATCH 0/3 being
> the cover letter)


Yes please.  Also please don't send html email (the lists reject it) and
don't top post :)

thanks,

greg k-h

  parent reply	other threads:[~2026-05-15 12:33 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-15  1:33 [PATCH 1/4] staging: rtl8723bs: reformat rtw_efuse_read_1_byte() signature Moksh Panicker
2026-05-15  1:33 ` [PATCH 2/4] staging: rtl8723bs: add braces to else clause in rtw_efuse.c Moksh Panicker
2026-05-15  1:33 ` [PATCH 3/4] staging: rtl8723bs: reformat rtw_efuse_one_byte_read() signature Moksh Panicker
2026-05-15  6:06 ` [PATCH 1/4] staging: rtl8723bs: reformat rtw_efuse_read_1_byte() signature Greg KH
     [not found]   ` <CAK0z5OmSunDp2xVhwEcy+gYz7KCXPihSV3R4zLn-ia39Lbtirg@mail.gmail.com>
2026-05-15 12:33     ` Greg KH [this message]
  -- strict thread matches above, loose matches on Subject: below --
2026-05-16  9:51 Moksh Panicker
2026-05-16 10:27 ` Greg KH

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=2026051503-crudely-mossy-19f9@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=linux-staging@lists.linux.dev \
    --cc=mokshpanicker.7@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.