From: Prarit Bhargava <prarit@redhat.com>
To: "Jiang, Dave" <dave.jiang@intel.com>
Cc: "der.herr@hofr.at" <der.herr@hofr.at>,
"Williams, Dan J" <dan.j.williams@intel.com>,
"dmaengine@vger.kernel.org" <dmaengine@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"rashika.kheria@gmail.com" <rashika.kheria@gmail.com>,
"Koul, Vinod" <vinod.koul@intel.com>,
"josh@joshtriplett.org" <josh@joshtriplett.org>
Subject: Re: [PATCH] ioat: fail self-test if wait_for_completion times out
Date: Wed, 07 Jan 2015 07:46:43 -0500 [thread overview]
Message-ID: <54AD2AB3.9030801@redhat.com> (raw)
In-Reply-To: <1420558682.62574.2.camel@djiang5-desk2.amr.corp.intel.com>
On 01/06/2015 10:38 AM, Jiang, Dave wrote:
>>>> - if (dma->device_tx_status(dma_chan, cookie, NULL) != DMA_COMPLETE) {
>>>> + if (tmo == 0 || dma->device_tx_status(dma_chan, cookie, NULL)
>>>> + != DMA_COMPLETE) {
>>>
>>> Can you please do:
>>> + if (tmo == 0 ||
>>> + dma->device_tx_status(dma_chan, cookie, NULL) != DMA_COMPLETE) {
>>
>> Documentation/CodingStyle:Chapter 2
>>
>> "Statements longer than 80 columns will be broken into sensible chunks, unless
>> exceeding 80 columns significantly increases readability and does not hide
>> information. Descendants are always substantially shorter than the parent and
>> are placed substantially to the right. The same applies to function headers..."
>>
>> am I misreading the CodingStyle here ?
>
> I'm not sure what the issue is here.... What I proposed is still the
> same length as the original code. And what I suggested complies with the
> existing coding style that's already there.
Ugh ... I missed this obvious CodingStyle error.
What Dave is trying to say is that he (and I'm pretty sure everyone else
for that matter) disagree with you style change because you have not broken
the columns into "sensible chunks".
IOW ... this,
if (tmo == 0 ||
dma->device_tx_status(dma_chan, cookie, NULL) != DMA_COMPLETE) {
is much easier to comprehend than this,
if (tmo == 0 || dma->device_tx_status(dma_chan, cookie, NULL)
!= DMA_COMPLETE) {
P.
next prev parent reply other threads:[~2015-01-07 12:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-28 10:37 [PATCH] ioat: fail self-test if wait_for_completion times out Nicholas Mc Guire
2015-01-02 11:47 ` Prarit Bhargava
2015-01-05 16:51 ` Jiang, Dave
2015-01-06 0:42 ` Nicholas Mc Guire
2015-01-06 15:38 ` Jiang, Dave
2015-01-07 12:46 ` Prarit Bhargava [this message]
2015-01-07 13:09 ` Nicholas Mc Guire
2015-01-07 16:22 ` Jiang, Dave
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=54AD2AB3.9030801@redhat.com \
--to=prarit@redhat.com \
--cc=dan.j.williams@intel.com \
--cc=dave.jiang@intel.com \
--cc=der.herr@hofr.at \
--cc=dmaengine@vger.kernel.org \
--cc=josh@joshtriplett.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rashika.kheria@gmail.com \
--cc=vinod.koul@intel.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;
as well as URLs for NNTP newsgroup(s).