From: David Miller <davem@davemloft.net>
To: jeremy.linton@arm.com
Cc: nico@fluxnic.net, robert.jarzmik@free.fr,
felipe.balbi@linux.intel.com, fw@strlen.de, arnd@arndb.de,
steve.capper@arm.com, netdev@vger.kernel.org
Subject: Re: [PATCH v2] net: smc91x: ACPI Enable lan91x adapters
Date: Mon, 11 Jul 2016 13:50:25 -0700 (PDT) [thread overview]
Message-ID: <20160711.135025.1930714483564343208.davem@davemloft.net> (raw)
In-Reply-To: <1468250920-29814-1-git-send-email-jeremy.linton@arm.com>
From: Jeremy Linton <jeremy.linton@arm.com>
Date: Mon, 11 Jul 2016 10:28:40 -0500
> Enable lan91x adapters in some ARM machines and models
> when booted with an ACPI kernel.
>
> Signed-off-by: Jeremy Linton <jeremy.linton@arm.com>
Applied to net-next, thanks.
prev parent reply other threads:[~2016-07-11 20:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-11 15:28 [PATCH v2] net: smc91x: ACPI Enable lan91x adapters Jeremy Linton
2016-07-11 20:50 ` 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=20160711.135025.1930714483564343208.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=arnd@arndb.de \
--cc=felipe.balbi@linux.intel.com \
--cc=fw@strlen.de \
--cc=jeremy.linton@arm.com \
--cc=netdev@vger.kernel.org \
--cc=nico@fluxnic.net \
--cc=robert.jarzmik@free.fr \
--cc=steve.capper@arm.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).