From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
To: David Miller <davem@davemloft.net>
Cc: netdev@vger.kernel.org, linux-renesas-soc@vger.kernel.org,
linux-sh@vger.kernel.org
Subject: Re: [PATCH v2 0/7] sh_eth: implement simple RX checksum offload
Date: Tue, 5 Feb 2019 11:00:45 +0300 [thread overview]
Message-ID: <91342300-82c0-01c8-93cf-98d78827ebca@cogentembedded.com> (raw)
In-Reply-To: <20190204.133136.1764517040498341680.davem@davemloft.net>
On 05.02.2019 0:31, David Miller wrote:
>> Here's a set of 7 patches against DaveM's 'net-next.git' repo. I'm implemeting
>> the simple RX checksum offload (like was done for the 'ravb' driver by Simon
>> Horman); it has been only tested on the R8A7740 and R8A77980 SoCs, the other
>> SoCs should just work (according to their manuals)...
>
> Series applied, thanks.
>
> There was a "tha" --> "the" typo in one of your commit messages which I
> fixed up.
Indeed! Thank you. :-)
MBR, Sergei
prev parent reply other threads:[~2019-02-05 8:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-04 18:01 [PATCH v2 0/7] sh_eth: implement simple RX checksum offload Sergei Shtylyov
2019-02-04 18:05 ` [PATCH v2 1/7] sh_eth: rename sh_eth_cpu_data::hw_checksum Sergei Shtylyov
2019-02-04 18:06 ` [PATCH v2 2/7] sh_eth: RX checksum offload support Sergei Shtylyov
2019-02-04 18:07 ` [PATCH v2 3/7] sh_eth: offload RX checksum on R7S72100 Sergei Shtylyov
2019-02-04 18:08 ` [PATCH v2 4/7] sh_eth: offload RX checksum on R8A7740 Sergei Shtylyov
2019-02-04 18:10 ` [PATCH v2 5/7] sh_eth: offload RX checksum on R8A77980 Sergei Shtylyov
2019-02-04 18:11 ` [PATCH v2 6/7] sh_eth: offload RX checksum on SH7734 Sergei Shtylyov
2019-02-04 18:12 ` [PATCH v2 7/7] sh_eth: offload RX checksum on SH7763 Sergei Shtylyov
2019-02-04 21:31 ` [PATCH v2 0/7] sh_eth: implement simple RX checksum offload David Miller
2019-02-05 8:00 ` Sergei Shtylyov [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=91342300-82c0-01c8-93cf-98d78827ebca@cogentembedded.com \
--to=sergei.shtylyov@cogentembedded.com \
--cc=davem@davemloft.net \
--cc=linux-renesas-soc@vger.kernel.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