From: Paulo Miguel Almeida <paulo.miguel.almeida.rodenas@gmail.com>
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: gregkh@linuxfoundation.org, realwakka@gmail.com,
linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: pi433: remove rf69_get_flag function resolving enum conflict
Date: Wed, 2 Mar 2022 22:07:51 +1300 [thread overview]
Message-ID: <Yh8z5zWfpVKWNYpQ@mail.google.com> (raw)
In-Reply-To: <20220228063238.GA2794@kadam>
On Mon, Feb 28, 2022 at 09:32:38AM +0300, Dan Carpenter wrote:
> Looks good.
>
> Reviewed-by: Dan Carpenter <dan.carpenter@oracle.com>
>
Thanks for reviewing my patch Dan.
> > 4 files changed, 4 insertions(+), 69 deletions(-)
>
> You don't really need to write a long commit message for a commit which
> deletes 69 - 4 = 65 lines. Just say "Remove pointless rf69_get_flag()
> function and call rf69_read_reg() directly. This cleanup removes 65
> lines of code and it more obvious to read."
>
Thanks for the feedback. I swear I don't do that on purpose ... I have always
struggled to be succint tbh. It's just something I'm actively working on...
> > - rf69_get_flag(dev->spi,
> > - rssi_exceeded_threshold));
> > + rf69_read_reg(spi, REG_IRQFLAGS1)
> > + & MASK_IRQFLAGS1_RSSI);
>
> The & character should go on the first line.
>
> rf69_read_reg(spi, REG_IRQFLAGS1) &
> MASK_IRQFLAGS1_RSSI);
>
> But that can be done in a follow on patch if you want. Or you can
> leave it as-is.
>
Noted. this patch was already merged into the staging-testing. I will
send another one fixing it.
Best regards,
Paulo Almeida
prev parent reply other threads:[~2022-03-02 9:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-25 22:40 Paulo Miguel Almeida
2022-02-28 6:32 ` Dan Carpenter
2022-03-02 9:07 ` Paulo Miguel Almeida [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=Yh8z5zWfpVKWNYpQ@mail.google.com \
--to=paulo.miguel.almeida.rodenas@gmail.com \
--cc=dan.carpenter@oracle.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=realwakka@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
all inboxes | Powered by JetHome®