From: Soumya Negi <soumya.negi97@gmail.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Micky Ching <micky_ching@realsil.com.cn>
Cc: outreachy@lists.linux.dev, linux-staging@lists.linux.dev,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] staging: rts5208: Fix checkpatch macro warnings
Date: Fri, 13 Oct 2023 00:46:31 -0700 [thread overview]
Message-ID: <20231013074630.GB13814@Negi> (raw)
In-Reply-To: <cover.1697113047.git.soumya.negi97@gmail.com>
On Thu, Oct 12, 2023 at 05:50:21AM -0700, Soumya Negi wrote:
> In the driver staging/rts5208, checkpatch.pl warns of possible precedence
> issues in the header rtsx.h because macro arguments are not parenthesized.
> This patch set handles the respective macros differently(as needed) in
> each patch to fix the warnings. Patches can be applied in any order.
>
> Soumya Negi (2):
> staging: rts5208: Refactor macros to static inline functions
> staging: rts5208: Remove macros scsi_lock(), scsi_unlock()
>
> drivers/staging/rts5208/rtsx.c | 24 ++++++-------
> drivers/staging/rts5208/rtsx.h | 66 ++++++++++++++++++++--------------
> 2 files changed, 52 insertions(+), 38 deletions(-)
Please ignore this patch set. Its incomplete & the rest of the patches
were not sent successfully. I have successfuly resent the complete
patchset(unchanged) as v2 with an explanation after --- in the cover patch.
> --
> 2.17.1
>
prev parent reply other threads:[~2023-10-13 7:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-12 12:50 [PATCH 0/2] staging: rts5208: Fix checkpatch macro warnings Soumya Negi
2023-10-13 7:46 ` Soumya Negi [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=20231013074630.GB13814@Negi \
--to=soumya.negi97@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=micky_ching@realsil.com.cn \
--cc=outreachy@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