From: Ben Hutchings <ben.hutchings@codethink.co.uk>
To: "David S.Miller" <davem@davemloft.net>
Cc: netdev@vger.kernel.org, linux-kernel@lists.codethink.co.uk,
Nobuhiro Iwamatsu <nobuhiro.iwamatsu.yj@renesas.com>,
Mitsuhiro Kimura <mitsuhiro.kimura.kc@renesas.com>,
Hisashi Nakamura <hisashi.nakamura.ak@renesas.com>,
Yoshihiro Kaneko <ykaneko0929@gmail.com>
Subject: [PATCH kernel 0/4] Fixes for sh_eth #3
Date: Tue, 27 Jan 2015 00:40:32 +0000 [thread overview]
Message-ID: <1422319232.3524.14.camel@xylophone.i.decadent.org.uk> (raw)
I'm continuing review and testing of Ethernet support on the R-Car H2
chip. This series fixes the last of the more serious issues I've found.
These are not tested on any of the other supported chips.
Ben.
Ben Hutchings (4):
sh_eth: Remove RX overflow log messages
sh_eth: Ensure DMA engines are stopped before freeing buffers
sh_eth: Check for DMA mapping errors on transmit
sh_eth: Fix DMA-API usage for RX buffers
drivers/net/ethernet/renesas/sh_eth.c | 80 ++++++++++++++++++++++++---------
1 file changed, 59 insertions(+), 21 deletions(-)
--
1.7.10.4
next reply other threads:[~2015-01-27 0:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-27 0:40 Ben Hutchings [this message]
2015-01-27 0:41 ` [PATCH kernel 1/4] sh_eth: Remove RX overflow log messages Ben Hutchings
2015-01-27 0:49 ` [PATCH kernel 2/4] sh_eth: Ensure DMA engines are stopped before freeing buffers Ben Hutchings
2015-01-27 0:49 ` [PATCH kernel 3/4] sh_eth: Check for DMA mapping errors on transmit Ben Hutchings
2015-01-27 0:50 ` [PATCH kernel 4/4] sh_eth: Fix DMA-API usage for RX buffers Ben Hutchings
2015-02-27 20:36 ` Sergei Shtylyov
2015-02-28 3:06 ` Ben Hutchings
2015-01-27 0:51 ` [Linux-kernel] [PATCH kernel 0/4] Fixes for sh_eth #3 Ben Hutchings
2015-01-27 8:19 ` David Miller
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=1422319232.3524.14.camel@xylophone.i.decadent.org.uk \
--to=ben.hutchings@codethink.co.uk \
--cc=davem@davemloft.net \
--cc=hisashi.nakamura.ak@renesas.com \
--cc=linux-kernel@lists.codethink.co.uk \
--cc=mitsuhiro.kimura.kc@renesas.com \
--cc=netdev@vger.kernel.org \
--cc=nobuhiro.iwamatsu.yj@renesas.com \
--cc=ykaneko0929@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.