From: Juliana Rodrigues <juliana.orod@gmail.com>
To: Julia Lawall <julia.lawall@lip6.fr>
Cc: outreachy-kernel@googlegroups.com
Subject: Re: [Outreachy kernel] [PATCH v2] staging: dgnc: fixed spaces before and after "|"
Date: Sun, 13 Mar 2016 02:40:05 -0300 [thread overview]
Message-ID: <1457847605.12864.3.camel@gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1603130632380.2069@localhost6.localdomain6>
Em Dom, 2016-03-13 às 06:33 +0100, Julia Lawall escreveu:
> On Sun, 13 Mar 2016, Juliana Rodrigues wrote:
>
> > This patch fixes the following issue while mantains
> > 80 character per line limit by removing
> > unnecessary parenthesis.
> >
> > CHECK: spaces preferred around that '|' (ctx:VxV)
> > +
> writeb((UART_FCR_ENABLE_FIFO|UART_FCR_CLEAR_RCVR|UART_FCR_CLEAR_XMIT)
> ,
> >
> > Signed-off-by: Juliana Rodrigues <juliana.orod@gmail.com>
> > ---
> > Changes on v2:
> > - Removed file name from subject line
> > ---
> > drivers/staging/dgnc/dgnc_cls.c | 6 ++++--
> > 1 file changed, 4 insertions(+), 2 deletions(-)
> >
> > diff --git a/drivers/staging/dgnc/dgnc_cls.c
> b/drivers/staging/dgnc/dgnc_cls.c
> > index 51db98b..6e1e475 100644
> > --- a/drivers/staging/dgnc/dgnc_cls.c
> > +++ b/drivers/staging/dgnc/dgnc_cls.c
> > @@ -1168,8 +1168,10 @@ static void cls_uart_init(struct channel_t
> *ch)
> > /* Clear out UART and FIFO */
> > readb(&ch->ch_cls_uart->txrx);
> >
> >
> - writeb((UART_FCR_ENABLE_FIFO|UART_FCR_CLEAR_RCVR|UART_FCR_CLEAR
> _XMIT),
> > - &ch->ch_cls_uart->isr_fcr);
> > + writeb((UART_FCR_ENABLE_FIFO |
> > + UART_FCR_CLEAR_RCVR |
> > + UART_FCR_CLEAR_XMIT),
>
> So it couldn't fit on one line? Or not even on two lines?
Actually, I forgot to add the changes into this patch, sorry.
I sent a new one to fix this.
>
> > + &ch->ch_cls_uart->isr_fcr);
>
> This line should not have been affected by the patch. It has been
> indented by one more space to make it look like it is part of the |
> rather
> than an argument of writeb.
>
> julia
>
> > udelay(10);
> >
> > ch->ch_flags |= (CH_FIFO_ENABLED | CH_TX_FIFO_EMPTY |
> CH_TX_FIFO_LWM);
> > --
> > 2.7.2
> >
> > --
> > You received this message because you are subscribed to the Google
> Groups "outreachy-kernel" group.
> > To unsubscribe from this group and stop receiving emails from it,
> send an email to outreachy-kernel+unsubscribe@googlegroups.com.
> > To post to this group, send email to outreachy-kernel@googlegroups.
> com.
> > To view this discussion on the web visit https://groups.google.com/
> d/msgid/outreachy-kernel/20160313052049.GA12145%40spock.
> > For more options, visit https://groups.google.com/d/optout.
> >
prev parent reply other threads:[~2016-03-13 5:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20160313052049.GA12145@spock>
2016-03-13 5:33 ` [Outreachy kernel] [PATCH v2] staging: dgnc: fixed spaces before and after "|" Julia Lawall
2016-03-13 5:40 ` Juliana Rodrigues [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=1457847605.12864.3.camel@gmail.com \
--to=juliana.orod@gmail.com \
--cc=julia.lawall@lip6.fr \
--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.