From: Ben Dooks <ben.dooks@codethink.co.uk>
To: Yoshihiro Shimoda <yoshihiro.shimoda.uh@renesas.com>,
cm-hiep@jinso.co.jp
Cc: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>,
netdev@vger.kernel.org, linux-sh@vger.kernel.org,
Magnus Damm <magnus.damm@gmail.com>,
Simon Horman <horms@verge.net.au>
Subject: Re: Ethernet bug at Upstream-v3.15-rcx on Lager.
Date: Fri, 30 May 2014 14:04:34 +0000 [thread overview]
Message-ID: <53888FF2.8040505@codethink.co.uk> (raw)
In-Reply-To: <5375A877.1090606@renesas.com>
On 16/05/14 06:56, Yoshihiro Shimoda wrote:
> Hi Hiep-san,
>
> (2014/05/16 10:08), カオ ミン ヒェップ wrote:
>>>
>>>> Please review it when you have time.
>>>
>>> Please try this patch:
>>>
>>> http://marc.info/?l=linux-netdev&m\x139602519809181
>>>
>> I have tested this patch on v3.15.0-rc5-00077-g14186fe, and results are the message of
>> "sh-eth r8a7790-ether eth0: Receive FIFO Overflow" has disappeared and sending datagrams is good.
>> (Bandwidth 10M to 100M: Test with 5/5 times by script and by hand are good)
>>
>
> It's nice!
> So, I hope the patch is merged in upstream.
> However, the patch's change log mentioned r8a7790 only.
> The r8a7791's ethernet controller also has this bit.
The bit update covers both of them as the r8a7790 and r8a7791 both share
the same configuration structure.
I re-sent the patch but didn't find your email post until after I had
sent it, otherwise I would have mentioned your testing specifically. In
future it would be helpful if you could do the following
- Mention driver by name in the subject line
- Search the list for previous mentions and reply to that/those threads.
--
Ben Dooks http://www.codethink.co.uk/
Senior Engineer Codethink - Providing Genius
next prev parent reply other threads:[~2014-05-30 14:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-15 6:28 Ethernet bug at Upstream-v3.15-rcx on Lager カオ ミン ヒェップ
2014-05-15 17:20 ` Sergei Shtylyov
2014-05-16 1:08 ` カオ ミン ヒェップ
2014-05-16 5:56 ` Yoshihiro Shimoda
2014-05-30 14:04 ` Ben Dooks [this message]
2014-06-03 2:43 ` Yoshihiro Shimoda
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=53888FF2.8040505@codethink.co.uk \
--to=ben.dooks@codethink.co.uk \
--cc=cm-hiep@jinso.co.jp \
--cc=horms@verge.net.au \
--cc=linux-sh@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=sergei.shtylyov@cogentembedded.com \
--cc=yoshihiro.shimoda.uh@renesas.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).