From: David Miller <davem@redhat.com>
To: niklas.soderlund+renesas@ragnatech.se
Cc: sergei.shtylyov@cogentembedded.com, horms+renesas@verge.net.au,
netdev@vger.kernel.org, linux-renesas-soc@vger.kernel.org,
geert@linux-m68k.org, linux-pm@vger.kernel.org
Subject: Re: [PATCHv3 0/6] sh_eth: add wake-on-lan support via magic packet
Date: Mon, 09 Jan 2017 15:55:42 -0500 (EST) [thread overview]
Message-ID: <20170109.155542.1563572267512721426.davem@redhat.com> (raw)
In-Reply-To: <20170109153409.13956-1-niklas.soderlund+renesas@ragnatech.se>
From: Niklas Söderlund <niklas.soderlund+renesas@ragnatech.se>
Date: Mon, 9 Jan 2017 16:34:03 +0100
> This series adds support for Wake-on-Lan using Magic Packet for a few
> models of the sh_eth driver. Patch 1/6 fix a naming error, patch 2/6
> adds generic support to control and support WoL while patches 3/6 - 6/6
> enable different models.
>
> Based ontop of net-next master.
...
Series applied, thanks.
next prev parent reply other threads:[~2017-01-09 20:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-09 15:34 [PATCHv3 0/6] sh_eth: add wake-on-lan support via magic packet Niklas Söderlund
2017-01-09 15:34 ` [PATCHv3 1/6] sh_eth: use correct name for ECMR_MPDE bit Niklas Söderlund
2017-01-09 15:34 ` [PATCHv3 2/6] sh_eth: add generic wake-on-lan support via magic packet Niklas Söderlund
2017-01-12 12:55 ` Sergei Shtylyov
2017-01-09 15:34 ` [PATCHv3 3/6] sh_eth: enable wake-on-lan for R-Car Gen2 devices Niklas Söderlund
2017-01-09 15:34 ` [PATCHv3 4/6] sh_eth: enable wake-on-lan for r8a7740/armadillo Niklas Söderlund
2017-01-09 15:34 ` [PATCHv3 5/6] sh_eth: enable wake-on-lan for sh7734 Niklas Söderlund
2017-01-09 15:34 ` [PATCHv3 6/6] sh_eth: enable wake-on-lan for sh7763 Niklas Söderlund
2017-01-09 20:55 ` David Miller [this message]
2017-01-09 21:48 ` [PATCHv3 0/6] sh_eth: add wake-on-lan support via magic packet Sergei Shtylyov
2017-01-09 21:55 ` 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=20170109.155542.1563572267512721426.davem@redhat.com \
--to=davem@redhat.com \
--cc=geert@linux-m68k.org \
--cc=horms+renesas@verge.net.au \
--cc=linux-pm@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=niklas.soderlund+renesas@ragnatech.se \
--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).