From: Nandha Kumar Singaram <nandhakumar.singaram@gmail.com>
To: Dan Carpenter <dan.carpenter@linaro.org>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: rts5208: Replace the occurrences of (1<<x) by BIT(x)
Date: Tue, 17 Oct 2023 07:02:00 -0700 [thread overview]
Message-ID: <20231017140200.GA3156@ubuntu> (raw)
In-Reply-To: <a45368a0-6f7c-4401-804d-1ff3cb8803b7@kadam.mountain>
On Tue, Oct 17, 2023 at 07:06:02AM +0300, Dan Carpenter wrote:
> Btw, eventually if we fix enough checkpatch warnings, then eventually we
> get to a point where all the remaining warnings are wrong. Like we've
> fixed everything checkpatch gets correct and only wrong things are left.
> So just be aware of that, that sometimes everything checkpatch suggests
> is wrong.
>
> regards,
> dan carpenter
>
Thanks for the feedback dan.
next prev parent reply other threads:[~2023-10-17 14:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-16 20:11 [PATCH] staging: rts5208: Replace the occurrences of (1<<x) by BIT(x) Nandha Kumar Singaram
2023-10-17 4:02 ` Dan Carpenter
2023-10-17 4:06 ` Dan Carpenter
2023-10-17 14:02 ` Nandha Kumar Singaram [this message]
2023-10-17 14:14 ` Nandha Kumar Singaram
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=20231017140200.GA3156@ubuntu \
--to=nandhakumar.singaram@gmail.com \
--cc=dan.carpenter@linaro.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 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.