From: Dan Carpenter <dan.carpenter@oracle.com>
To: Daeseok Youn <daeseok.youn@gmail.com>
Cc: gregkh@linuxfoundation.org, devel@driverdev.osuosl.org,
nandu.hgowda@gmail.com, sachin.kamat@linaro.org,
peter.p.waskiewicz.jr@intel.com, linux-kernel@vger.kernel.org,
himangi774@gmail.com, fempsci@gmail.com
Subject: Re: [PATCH 2/3] Staging: cxt1e1: Fix line length over 80 characters in musycc.c
Date: Fri, 9 May 2014 11:07:06 +0300 [thread overview]
Message-ID: <20140509080706.GK26890@mwanda> (raw)
In-Reply-To: <20140509013948.GA30935@devel.8.8.4.4>
This patch is ok, but here are some additional hints.
On Fri, May 09, 2014 at 10:39:48AM +0900, Daeseok Youn wrote:
> @@ -1100,7 +1102,9 @@ musycc_bh_rx_eom(mpi_t *pi, int gchan)
> */
> if (hdlcnum >= 228) {
> if (nciProcess_RX_packet)
> - (*nciProcess_RX_packet) (hdlcnum, status & 0x3fff, m, ch->user);
> + (*nciProcess_RX_packet)(hdlcnum, status &
> + 0x3fff, m,
> + ch->user);
It's possible to break this one up at the commas.
(*nciProcess_RX_packet)(hdlcnum,
status & 0x3fff,
m, ch->user);
> } else
> #endif /* CONFIG_SBE_WAN256T3_NCOMM */
> {
> @@ -1379,7 +1383,8 @@ musycc_intr_bh_tasklet(ci_t *ci)
> else
> ci->iqd_p[headx] =
> __constant_cpu_to_le32(INT_EMPTY_ENTRY);
> - ci->iqp_headx = (headx + 1) & (INT_QUEUE_SIZE - 1); /* insure wrapness */
> + /* insure wrapness */
> + ci->iqp_headx = (headx + 1) & (INT_QUEUE_SIZE - 1);
> FLUSH_MEM_WRITE();
> FLUSH_MEM_READ();
> continue;
> @@ -1516,7 +1521,8 @@ musycc_intr_bh_tasklet(ci_t *ci)
> pr_info("%s: RX buffer overflow [ONR] on channel %d, mode %x\n",
> ci->devname, ch->channum,
> ch->p.chan_mode);
> - //musycc_dump_rxbuffer_ring (ch, 0); /* RLD DEBUG */
> + /* RLD DEBUG */
> + //musycc_dump_rxbuffer_ring (ch, 0);
Just delete this commented out code.
> }
> }
> musycc_chan_restart(ch);
> @@ -1573,7 +1579,8 @@ musycc_intr_bh_tasklet(ci_t *ci)
> } /* switch on err */
>
> /* Check for interrupt lost condition */
> - if ((currInt & INTRPT_ILOST_M) && (cxt1e1_log_level >= LOG_ERROR))
> + if ((currInt & INTRPT_ILOST_M) &&
> + (cxt1e1_log_level >= LOG_ERROR))
> pr_info("%s: Interrupt queue overflow - ILOST asserted\n",
> ci->devname);
> /* insure wrapness */
> @@ -1684,7 +1691,8 @@ musycc_del_chan(ci_t *ci, int channum)
> {
> mch_t *ch;
>
> - if ((channum < 0) || (channum >= (MUSYCC_NPORTS * MUSYCC_NCHANS))) /* sanity chk param */
> + /* sanity chk param */
This kind of comment is too obvious. Just delete it.
> + if ((channum < 0) || (channum >= (MUSYCC_NPORTS * MUSYCC_NCHANS)))
> return ECHRNG;
> ch = sd_find_chan(ci, channum);
> if (!ch)
regards,
dan carpenter
next prev parent reply other threads:[~2014-05-09 8:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-09 1:39 [PATCH 2/3] Staging: cxt1e1: Fix line length over 80 characters in musycc.c Daeseok Youn
2014-05-09 8:07 ` Dan Carpenter [this message]
2014-05-09 8:26 ` DaeSeok Youn
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=20140509080706.GK26890@mwanda \
--to=dan.carpenter@oracle.com \
--cc=daeseok.youn@gmail.com \
--cc=devel@driverdev.osuosl.org \
--cc=fempsci@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=himangi774@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nandu.hgowda@gmail.com \
--cc=peter.p.waskiewicz.jr@intel.com \
--cc=sachin.kamat@linaro.org \
/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;
as well as URLs for NNTP newsgroup(s).