From: David Miller <davem@davemloft.net>
To: sergei.shtylyov@cogentembedded.com
Cc: netdev@vger.kernel.org, linux-sh@vger.kernel.org
Subject: Re: [PATCH 0/2] sh_eth: remove unused BE descriptor support
Date: Mon, 04 Jan 2016 21:11:28 +0000 [thread overview]
Message-ID: <20160104.161128.2202956416981407539.davem@davemloft.net> (raw)
In-Reply-To: <27915743.MLN0FvErP3@wasted.cogentembedded.com>
From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
Date: Mon, 28 Dec 2015 02:05:24 +0300
> Here's a set of 2 patches against DaveM's 'net-next.git' repo plus the
> recently merged to 'net.git' repo fix for the 16-bit descriptor endianness.
> We get rid of ~30 LoCs and ~300 bytes of code.
Series applied, thanks Sergei.
prev parent reply other threads:[~2016-01-04 21:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-27 23:05 [PATCH 0/2] sh_eth: remove unused BE descriptor support Sergei Shtylyov
2015-12-27 23:07 ` [PATCH 1/2] sh_eth: remove EDMAC_BIG_ENDIAN Sergei Shtylyov
2015-12-28 5:32 ` Simon Horman
2015-12-27 23:10 ` [PATCH 2/2] sh_eth: get rid of {cpu|edmac}_to_{edmac|cpu}() Sergei Shtylyov
2015-12-28 5:32 ` Simon Horman
2016-01-04 21:11 ` 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=20160104.161128.2202956416981407539.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=linux-sh@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=sergei.shtylyov@cogentembedded.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).