From: Arnd Bergmann <arnd@arndb.de>
To: Scott Branden <scott.branden@broadcom.com>
Cc: Russell King <linux@armlinux.org.uk>,
Olof Johansson <olof@lixom.net>,
Florian Fainelli <f.fainelli@gmail.com>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
BCM Kernel Feedback <bcm-kernel-feedback-list@broadcom.com>,
Ray Jui <rjui@broadcom.com>
Subject: Re: [PATCH] ARM: multi_v7_defconfig: Enable Intel e1000e driver
Date: Mon, 10 Oct 2016 09:47:47 +0200 [thread overview]
Message-ID: <8265935.TobkRj9BnG@wuerfel> (raw)
In-Reply-To: <1475959264-16582-1-git-send-email-scott.branden@broadcom.com>
On Saturday, October 8, 2016 1:41:04 PM CEST Scott Branden wrote:
> Enable support for the Intel e1000e driver
>
> Signed-off-by: Ray Jui <rjui@broadcom.com>
> Signed-off-by: Scott Branden <scott.branden@broadcom.com>
>
Can we make this a loadable module and group it with the other
ethernet drivers?
Arnd
WARNING: multiple messages have this Message-ID (diff)
From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: multi_v7_defconfig: Enable Intel e1000e driver
Date: Mon, 10 Oct 2016 09:47:47 +0200 [thread overview]
Message-ID: <8265935.TobkRj9BnG@wuerfel> (raw)
In-Reply-To: <1475959264-16582-1-git-send-email-scott.branden@broadcom.com>
On Saturday, October 8, 2016 1:41:04 PM CEST Scott Branden wrote:
> Enable support for the Intel e1000e driver
>
> Signed-off-by: Ray Jui <rjui@broadcom.com>
> Signed-off-by: Scott Branden <scott.branden@broadcom.com>
>
Can we make this a loadable module and group it with the other
ethernet drivers?
Arnd
next prev parent reply other threads:[~2016-10-10 7:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-08 20:41 [PATCH] ARM: multi_v7_defconfig: Enable Intel e1000e driver Scott Branden
2016-10-08 20:41 ` Scott Branden
2016-10-10 7:47 ` Arnd Bergmann [this message]
2016-10-10 7:47 ` Arnd Bergmann
2016-10-11 22:38 ` Scott Branden
2016-10-11 22:38 ` Scott Branden
2016-10-17 22:03 ` Olof Johansson
2016-10-17 22:03 ` Olof Johansson
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=8265935.TobkRj9BnG@wuerfel \
--to=arnd@arndb.de \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=f.fainelli@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=olof@lixom.net \
--cc=rjui@broadcom.com \
--cc=scott.branden@broadcom.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.