linux-staging.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: weibu@redadmin.org
To: Greg KH <gregkh@linuxfoundation.org>
Cc: linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: rtl8723bs: rtw_efuse.h: Fix prototype whitespace
Date: Mon, 15 Sep 2025 00:48:47 +0900	[thread overview]
Message-ID: <174fe5db36d1371c0c111c9b75729784@redadmin.org> (raw)
In-Reply-To: <1d0fdc3bde254057539b7e8506d0c211@redadmin.org>

Hi Greg,

Quick follow-up: after rebasing onto your staging.git `staging-testing`,
the change turned out to be already present and there’s no delta left.
Please ignore this patch; I won’t resend v2.

Thanks,
Akiyoshi

2025-09-15 00:29 に weibu@redadmin.org さんは書きました:
> Hi Greg,
> 
> Thanks for the heads-up. That patch was generated against linux-next
> (next-2025-09-12). I’ll rebase it onto your staging.git 
> `staging-testing`
> branch and resend it as v2.
> 
> Thanks,
> Akiyoshi
> 
> 2025-09-15 00:09 に Greg KH さんは書きました:
>> On Sat, Sep 13, 2025 at 08:24:58PM +0900, Akiyoshi Kurita wrote:
>>> Several function prototypes in rtw_efuse.h contained extra spaces
>>> between the type and variable name of the last argument.
>>> 
>>> Remove these spaces to conform to the kernel coding style.
>>> No functional change is intended.
>>> 
>>> Signed-off-by: Akiyoshi Kurita <weibu@redadmin.org>
>>> ---
>>>  drivers/staging/rtl8723bs/include/rtw_efuse.h | 6 +++---
>>>  1 file changed, 3 insertions(+), 3 deletions(-)
>> 
>> This does not apply to my current tree, what did you make it against?
>> 
>> thanks,
>> 
>> greg k-h

      reply	other threads:[~2025-09-14 15:48 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-13 11:24 [PATCH] staging: rtl8723bs: rtw_efuse.h: Fix prototype whitespace Akiyoshi Kurita
2025-09-14 15:09 ` Greg KH
2025-09-14 15:29   ` weibu
2025-09-14 15:48     ` weibu [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=174fe5db36d1371c0c111c9b75729784@redadmin.org \
    --to=weibu@redadmin.org \
    --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;
as well as URLs for NNTP newsgroup(s).