Netdev List
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: gerg@snapgear.com
Cc: netdev@vger.kernel.org, gerg@uclinux.org, s.hauer@pengutronix.de
Subject: Re: [PATCH] fec: fix FEC driver packet transmission breakage
Date: Sun, 09 Aug 2009 21:51:36 -0700 (PDT)	[thread overview]
Message-ID: <20090809.215136.256130746.davem@davemloft.net> (raw)
In-Reply-To: <200908070358.n773wIxB015388@localhost.localdomain>

From: Greg Ungerer <gerg@snapgear.com>
Date: Fri, 7 Aug 2009 13:58:18 +1000

> fec: fix FEC driver packet transmission breakage
> 
> Commit f0b3fbeae11a526c3d308b691684589ee37c359b 

In the future, when referencing commits, please also provide the
commit message header line text, in parenthesis, and in quotes, like
this ("the commit message header line"), right after the SHA1 ID.

I've fixed up your commit message, in that way, this time.  But
next time I'm going to simply shoot this back to you.

> breaks transmission of
> packets where the skb data buffer is not memory aligned according to
> FEC_ALIGNMENT. It incorrectly passes to dma_sync_single() the buffer
> address directly from the skb, instead of the address calculated for
> use (which may be the skb address or one of the bounce buffers).
> 
> It seems there is no use converting the cpu address of the buffer to
> a physical either, since dma_map_single() expects the cpu address and
> will return the dma address to use in the descriptor. So remove the use
> of __pa() on the buffer address as well.
> 
> This patch is against 2.6.30-rc5. This breakage is a regression over
> 2.6.30, which does not have this problem.
> 
> Signed-off-by: Greg Ungerer <gerg@uclinux.org>

Applied.

      reply	other threads:[~2009-08-10  4:51 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-07  3:58 [PATCH] fec: fix FEC driver packet transmission breakage Greg Ungerer
2009-08-10  4:51 ` David Miller [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=20090809.215136.256130746.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=gerg@snapgear.com \
    --cc=gerg@uclinux.org \
    --cc=netdev@vger.kernel.org \
    --cc=s.hauer@pengutronix.de \
    /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