From: Dan Carpenter <dan.carpenter@oracle.com>
To: Cristiane Naves <cristianenavescardoso09@gmail.com>
Cc: outreachy-kernel@googlegroups.com
Subject: Re: [PATCH v3 1/2] staging: rtl8712: Fix Alignment of open parenthesis
Date: Tue, 29 Oct 2019 10:51:24 +0300 [thread overview]
Message-ID: <20191029075123.GH1944@kadam> (raw)
In-Reply-To: <20191028212137.GC2311@cristiane-Inspiron-5420>
On Mon, Oct 28, 2019 at 06:21:37PM -0300, Cristiane Naves wrote:
> On Mon, Oct 28, 2019 at 10:02:59PM +0300, Dan Carpenter wrote:
> > On Mon, Oct 28, 2019 at 12:15:52PM -0300, Cristiane Naves wrote:
> > > Fix alignment should match open parenthesis. Issue found by checkpatch.
> > >
> > > Signed-off-by: Cristiane Naves <cristianenavescardoso09@gmail.com>
> > > ---
> > > drivers/staging/rtl8712/rtl8712_recv.c | 36 +++++++++++++++++-----------------
> > > 1 file changed, 18 insertions(+), 18 deletions(-)
> > >
> > > diff --git a/drivers/staging/rtl8712/rtl8712_recv.c b/drivers/staging/rtl8712/rtl8712_recv.c
> > > index af12c16..304d031 100644
> > > --- a/drivers/staging/rtl8712/rtl8712_recv.c
> > > +++ b/drivers/staging/rtl8712/rtl8712_recv.c
> > > @@ -61,13 +61,13 @@ void r8712_init_recv_priv(struct recv_priv *precvpriv,
> > > precvbuf->ref_cnt = 0;
> > > precvbuf->adapter = padapter;
> > > list_add_tail(&precvbuf->list,
> > > - &(precvpriv->free_recv_buf_queue.queue));
> > > + (&precvpriv->free_recv_buf_queue.queue));
> >
> > You did this correctly in v2.
> >
> > - &(precvpriv->free_recv_buf_queue.queue));
> > + &precvpriv->free_recv_buf_queue.queue);
> >
> > > precvbuf++;
> > > }
> > > precvpriv->free_recv_buf_queue_cnt = NR_RECVBUFF;
> > > tasklet_init(&precvpriv->recv_tasklet,
> >
> > regards,
> > dan carpenter
> >
> I wondered if it was better to use parentheses or not. Is it necessary
> to send a new v5 version containing this change or it's possible to get it from
> v2?
Greg said that patch 2/2 of v4 didn't apply. To me that suggests that
maybe he applied patch 1/2 and sent you an email? If not then redo it.
If you don't change the parenthese Greg will apply it. If you do then
maybe he will and maybe he won't. The rules say don't do that but we
let people bend the rules slightly. But why add that element of doubt?
I have a script which removes white space changes so if you change the
parentheses I have to check the patch by hand so that's annoying. But I
might not comment on it when I'm reviewing the patch.
My advice is to remove the parenthese in a separate patch.
It's not possible to get the patch from v2. Once a patch is gone then
it's gone forever.
regards,
dan carpenter
next prev parent reply other threads:[~2019-10-29 7:53 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-28 15:12 [PATCH v3 0/2] Cleanup in rtl8712 Cristiane Naves
2019-10-28 15:15 ` [PATCH v3 1/2] staging: rtl8712: Fix Alignment of open parenthesis Cristiane Naves
2019-10-28 19:02 ` Dan Carpenter
2019-10-28 21:21 ` Cristiane Naves
2019-10-29 7:51 ` Dan Carpenter [this message]
2019-10-29 8:05 ` [Outreachy kernel] " Greg KH
2019-10-29 8:15 ` Greg KH
2019-10-29 20:21 ` Cristiane Naves
2019-10-29 20:59 ` Julia Lawall
2019-10-29 21:06 ` Cristiane Naves
2019-10-30 5:58 ` Julia Lawall
2019-10-30 4:29 ` Dan Carpenter
2019-10-28 15:17 ` [PATCH v3 2/2] staging: rtl8712: Remove lines before a close brace Cristiane Naves
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=20191029075123.GH1944@kadam \
--to=dan.carpenter@oracle.com \
--cc=cristianenavescardoso09@gmail.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.