From: Johan Hovold <johan@kernel.org>
To: NIshka Dasgupta <nishka.dasgupta@yahoo.com>
Cc: Johan Hovold <johan@kernel.org>,
elder@kernel.org, gregkh@linuxfoundation.org,
outreachy-kernel@googlegroups.com
Subject: Re: [PATCH] staging: greybus: Remove parentheses around variable
Date: Wed, 20 Mar 2019 17:31:17 +0100 [thread overview]
Message-ID: <20190320163117.GA623@localhost> (raw)
In-Reply-To: <4d37053a-61c3-2eda-ae97-89e7c5ce787e@yahoo.com>
On Wed, Mar 20, 2019 at 09:32:01PM +0530, NIshka Dasgupta wrote:
>
>
> On 20/03/19 2:20 PM, Johan Hovold wrote:
> > On Wed, Mar 20, 2019 at 01:33:08AM +0530, Nishka Dasgupta wrote:
> >> Remove parentheses around variable.
> >
> > Perhaps
> >
> > Remove unnecessary parentheses around expression.
> >
> > would be more accurate.
> >
> >> Signed-off-by: Nishka Dasgupta <nishka.dasgupta@yahoo.com>
> >
> > But no need to resend unless you want to. If you do, you can add my ack
> > before your SoB-tag:
> >
> > Acked-by: Johan Hovold <johan@kernel.org>
>
> I would like to resend but I think this patch has already been added to
> staging-next, so I don't think I should send it again. I could if it's
> alright.
Greg's trees are generally immutable so once a patch has been applied
(and passed some initial testing) it cannot be replaced and the
corresponding code can only be fixed incrementally.
So no need to resend.
> Thank you for your initial suggestion though, and I'm sorry I wasn't
> sure about how to acknowledge your help in the patch itself.
No worries at all. And there's no need to give credit for minor review
feedback; reviewers may still provide their Reviewed-by or Acked-by tags
once they're happy with the patch though.
Thanks,
Johan
prev parent reply other threads:[~2019-03-20 16:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-19 20:03 [PATCH] staging: greybus: Remove parentheses around variable Nishka Dasgupta
2019-03-19 20:06 ` [Outreachy kernel] " Julia Lawall
2019-03-20 6:47 ` Greg KH
2019-03-20 6:58 ` Julia Lawall
2019-03-20 8:50 ` Johan Hovold
2019-03-20 16:02 ` NIshka Dasgupta
2019-03-20 16:31 ` Johan Hovold [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=20190320163117.GA623@localhost \
--to=johan@kernel.org \
--cc=elder@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=nishka.dasgupta@yahoo.com \
--cc=outreachy-kernel@googlegroups.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 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.