netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Govindarajulu Varadarajan <_govind@gmx.com>
To: David Miller <davem@davemloft.net>
Cc: nhorman@tuxdriver.com, _govind@gmx.com, netdev@vger.kernel.org,
	cooldavid@cooldavid.org
Subject: Re: [PATCH] jme: Fix DMA unmap warning
Date: Wed, 7 May 2014 02:34:55 +0530 (IST)	[thread overview]
Message-ID: <alpine.LNX.2.03.1405070230210.1428@ws.cisco> (raw)
In-Reply-To: <20140506.165347.1104086045678188867.davem@davemloft.net>



On Tue, 6 May 2014, David Miller wrote:

> From: Neil Horman <nhorman@tuxdriver.com>
> Date: Tue, 6 May 2014 16:50:46 -0400
>
>>>> +		ctxbi = txbi + ((startidx + j + 2) & (mask));
>>>> +		pci_unmap_page(jme->pdev,
>>>> +				ctxbi->mapping,
>>>> +				ctxbi->len,
>>>> +				PCI_DMA_TODEVICE);
>>>> +
>>>> +				ctxbi->mapping = 0;
>>>> +				ctxbi->len = 0;
>>>
>>> Alignment, a tab from 'for'
>> Not sure what you mean by this, I don't see any alignment errors above, or in my
>> tree.  Checkpatch also claims its clean.
>
> Indeed it is indented correctly, the "+" at the beginning of the line in
> the patch makes it look like it's not, but it is.
>

Hmm. This is how it looked when I applied the patch.
http://i.imgur.com/ZdjqJ3d.png

ctxbi->mapping = 0;
ctxbi->len = 0;

is aligned to '(' of pci_unmap_page. But these two statements are not arg of
the function. Shouldn't it be aligned along pci_unmap_page and not '('

Govind

  reply	other threads:[~2014-05-06 21:05 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-05 18:51 [PATCH] jme: Fix DMA unmap warning Neil Horman
2014-05-06 20:25 ` Govindarajulu Varadarajan
2014-05-06 20:50   ` Neil Horman
2014-05-06 20:53     ` David Miller
2014-05-06 21:04       ` Govindarajulu Varadarajan [this message]
2014-05-06 21:10         ` David Miller
2014-05-07 19:56 ` David Miller
2014-05-07 20:33   ` Neil Horman
2014-05-07 20:44     ` David Miller
2014-05-07 21:54       ` Neil Horman
2014-05-08  9:02     ` David Laight
2014-05-08 11:00       ` Neil Horman
2014-05-08 11:16         ` David Laight
2014-05-08 17:24       ` David Miller
2014-05-08 19:29   ` [RFC PATCH] net: Provide linear backoff mechanism for constrained resources at the driver Neil Horman
2014-05-09  8:55     ` David Laight
2014-05-09 11:17       ` Neil Horman
2014-05-09 12:53         ` David Laight
2014-05-09 15:33           ` Neil Horman
2014-05-09 15:46             ` David Laight
2014-05-09 17:02               ` Neil Horman
2014-05-18 16:19     ` Neil Horman
2014-05-21 18:05     ` Cong Wang
2014-05-21 18:49       ` Neil Horman
2014-05-11 12:49 ` [PATCH] jme: Fix DMA unmap warning Ben Hutchings
2014-05-11 13:04   ` Neil Horman

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=alpine.LNX.2.03.1405070230210.1428@ws.cisco \
    --to=_govind@gmx.com \
    --cc=cooldavid@cooldavid.org \
    --cc=davem@davemloft.net \
    --cc=netdev@vger.kernel.org \
    --cc=nhorman@tuxdriver.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).