From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
To: Denis Kirjanov <kda@linux-powerpc.org>
Cc: netdev@vger.kernel.org, linux-sh@vger.kernel.org
Subject: Re: [PATCH] sh_eth: fix typo in RX descriptor bit name
Date: Tue, 3 Nov 2015 22:35:15 +0300 [thread overview]
Message-ID: <56390C73.2030302@cogentembedded.com> (raw)
In-Reply-To: <CAOJe8K1GbJ7N9YW31f8Ht8Qbb2av_vpeZPv7R60DuKV6vuDZKA@mail.gmail.com>
Hello.
On 11/03/2015 10:30 PM, Denis Kirjanov wrote:
>> Commit 7d7355f58ba4 ("sh_eth: Ensure proper ordering of descriptor active
>> bit write/read") did the right thing but used too "heavy" barriers while
>> there were already "lighter" DMA barriers exactly for this case...
>>
>> Signed-off-by: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
>
> Fix the subject line...
Oops! Will fix in a jiffy...
(I thought at first that you're commenting on the already applied patch. :-))
MBR, Sergei
next prev parent reply other threads:[~2015-11-03 19:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-03 19:20 [PATCH] sh_eth: fix typo in RX descriptor bit name Sergei Shtylyov
2015-11-03 19:30 ` Denis Kirjanov
2015-11-03 19:35 ` Sergei Shtylyov [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-11-02 22:28 Sergei Shtylyov
2015-11-03 4:01 ` 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=56390C73.2030302@cogentembedded.com \
--to=sergei.shtylyov@cogentembedded.com \
--cc=kda@linux-powerpc.org \
--cc=linux-sh@vger.kernel.org \
--cc=netdev@vger.kernel.org \
/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).