public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Phillip Potter <phil@philpotter.co.uk>
To: Pavel Skripkin <paskripkin@gmail.com>
Cc: straube.linux@gmail.com, martin@kaiser.cx,
	saurav.girepunje@gmail.com, abdun.nihaal@gmail.com,
	linux-kernel@vger.kernel.org, linux-staging@lists.linux.dev
Subject: Re: [PATCH] staging: r8188eu: remove include/rtw_debug.h
Date: Fri, 20 May 2022 22:44:07 +0100	[thread overview]
Message-ID: <YogLpztabN6PkIT/@equinox> (raw)
In-Reply-To: <44d12b0f-3ce0-42d2-a475-31d70dd4d699@gmail.com>

On Sat, May 21, 2022 at 12:04:54AM +0300, Pavel Skripkin wrote:
> Hi Phillip,
> 
> On 5/20/22 01:10, Phillip Potter wrote:
> > Remove include/rtw_debug.h, as all it now has are:
> > 
> > (1) A load of unused preprocessor definitions that expand to BIT(x)
> >      variants.
> > (2) A preprocessor definition that expands to the name of the driver
> >      and is only used in one place inside a pr_info_once call in
> >      core/rtw_fw.c.
> > 
> > It is now surplus to requirements after fixing up the few places that
> > include the file.
> > 
> > Signed-off-by: Phillip Potter <phil@philpotter.co.uk>
> > ---
> >   drivers/staging/r8188eu/core/rtw_fw.c        |  4 +-
> >   drivers/staging/r8188eu/include/drv_types.h  |  1 -
> >   drivers/staging/r8188eu/include/rtw_debug.h  | 45 --------------------
> >   drivers/staging/r8188eu/os_dep/ioctl_linux.c |  1 -
> >   4 files changed, 2 insertions(+), 49 deletions(-)
> >   delete mode 100644 drivers/staging/r8188eu/include/rtw_debug.h
> > 
> > diff --git a/drivers/staging/r8188eu/core/rtw_fw.c b/drivers/staging/r8188eu/core/rtw_fw.c
> > index bf077876ed3d..0451e5177644 100644
> > --- a/drivers/staging/r8188eu/core/rtw_fw.c
> > +++ b/drivers/staging/r8188eu/core/rtw_fw.c
> > @@ -259,8 +259,8 @@ int rtl8188e_firmware_download(struct adapter *padapter)
> >   	fwhdr = (struct rt_firmware_hdr *)dvobj->firmware.data;
> >   	if (IS_FW_HEADER_EXIST(fwhdr)) {
> > -		pr_info_once("%sFirmware Version %d, SubVersion %d, Signature 0x%x\n",
> > -			     DRIVER_PREFIX, le16_to_cpu(fwhdr->version), fwhdr->subversion,
> > +		pr_info_once("R8188EU: Firmware Version %d, SubVersion %d, Signature 0x%x\n",
> > +			     le16_to_cpu(fwhdr->version), fwhdr->subversion,
> >   			     le16_to_cpu(fwhdr->signature));
> 
> What about converting this macro to dev_info_once()? IMO, looks cleaner:
> 
> [   27.985218] r8188eu 2-1:1.0: Firmware Version 11, SubVersion 1, Signature
> 0x88e1
> 
> 
> 
> 
> With regards,
> Pavel Skripkin

Hi Pavel,

Yes, good idea, I like it. This patch has been merged now, but I will
submit another to do this. Many thanks for the suggestion.

Regards,
Phil

      reply	other threads:[~2022-05-20 21:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-19 22:10 [PATCH] staging: r8188eu: remove include/rtw_debug.h Phillip Potter
2022-05-20 21:04 ` Pavel Skripkin
2022-05-20 21:44   ` Phillip Potter [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=YogLpztabN6PkIT/@equinox \
    --to=phil@philpotter.co.uk \
    --cc=abdun.nihaal@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-staging@lists.linux.dev \
    --cc=martin@kaiser.cx \
    --cc=paskripkin@gmail.com \
    --cc=saurav.girepunje@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