From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Zhengyi Shen <shenzhengyi@gmail.com>
Cc: Walt Feasel <waltfeasel@gmail.com>,
Afonso Bordado <afonsobordado@az8.co>,
Bhumika Goyal <bhumirks@gmail.com>, Arnd Bergmann <arnd@arndb.de>,
Anjali Menon <cse.anjalimenon@gmail.com>,
Dilek Uzulmez <dilekuzulmez@gmail.com>,
Gargi Sharma <gs051095@gmail.com>,
devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging/emxx_udc: Fix styling issues
Date: Fri, 3 Feb 2017 10:52:36 +0100 [thread overview]
Message-ID: <20170203095236.GB24767@kroah.com> (raw)
In-Reply-To: <20170202125654.32378-1-shenzhengyi@gmail.com>
On Thu, Feb 02, 2017 at 08:56:54PM +0800, Zhengyi Shen wrote:
> Fix line over 80 characters.
> Statements longer than 80 columns were broken into sensible chunks.
> Descendants in four different palces were in the same uniform style.
>
> Signed-off-by: Zhengyi Shen <shenzhengyi@gmail.com>
> ---
> drivers/staging/emxx_udc/emxx_udc.c | 13 ++++++++-----
> 1 file changed, 8 insertions(+), 5 deletions(-)
>
> diff --git a/drivers/staging/emxx_udc/emxx_udc.c b/drivers/staging/emxx_udc/emxx_udc.c
> index 77b242e..e771aee 100644
> --- a/drivers/staging/emxx_udc/emxx_udc.c
> +++ b/drivers/staging/emxx_udc/emxx_udc.c
> @@ -902,7 +902,8 @@ static int _nbu2ss_epn_out_pio(
> /* Copy of every four bytes */
> for (i = 0; i < iWordLength; i++) {
> pBuf32->dw =
> - _nbu2ss_readl(&preg->EP_REGS[ep->epnum - 1].EP_READ);
> + _nbu2ss_readl(
> + &preg->EP_REGS[ep->epnum - 1].EP_READ);
That's horrid, and not any better than the original code :(
> pBuf32++;
> }
> result = iWordLength * sizeof(u32);
> @@ -912,7 +913,8 @@ static int _nbu2ss_epn_out_pio(
> if (data > 0) {
> /*---------------------------------------------------------*/
> /* Copy of fraction byte */
> - Temp32.dw = _nbu2ss_readl(&preg->EP_REGS[ep->epnum - 1].EP_READ);
> + Temp32.dw =
> + _nbu2ss_readl(&preg->EP_REGS[ep->epnum - 1].EP_READ);
Same here, please leave the original as-is.
> for (i = 0 ; i < data ; i++)
> pBuf32->byte.DATA[i] = Temp32.byte.DATA[i];
> result += data;
> @@ -977,8 +979,8 @@ static int _nbu2ss_epn_out_transfer(
>
> /*-------------------------------------------------------------*/
> /* Receive Length */
> - iRecvLength
> - = _nbu2ss_readl(&preg->EP_REGS[num].EP_LEN_DCNT) & EPn_LDATA;
> + iRecvLength =
> + _nbu2ss_readl(&preg->EP_REGS[num].EP_LEN_DCNT) & EPn_LDATA;
>
> if (iRecvLength != 0) {
> result = _nbu2ss_epn_out_data(udc, ep, req, iRecvLength);
> @@ -2651,7 +2653,8 @@ static int nbu2ss_ep_queue(
> }
>
> req = container_of(_req, struct nbu2ss_req, req);
> - if (unlikely(!_req->complete || !_req->buf || !list_empty(&req->queue))) {
> + if (unlikely(!_req->complete || !_req->buf
> + || !list_empty(&req->queue))) {
odd indentation :(
prev parent reply other threads:[~2017-02-03 9:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-02 12:56 [PATCH] staging/emxx_udc: Fix styling issues Zhengyi Shen
2017-02-03 9:52 ` Greg Kroah-Hartman [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=20170203095236.GB24767@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=afonsobordado@az8.co \
--cc=arnd@arndb.de \
--cc=bhumirks@gmail.com \
--cc=cse.anjalimenon@gmail.com \
--cc=devel@driverdev.osuosl.org \
--cc=dilekuzulmez@gmail.com \
--cc=gs051095@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=shenzhengyi@gmail.com \
--cc=waltfeasel@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