From: Jeff Garzik <jeff@garzik.org>
To: Bryan Wu <cooloney@kernel.org>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
Mike Frysinger <vapier.adi@gmail.com>
Subject: Re: [PATCH 1/1] netdev: Blackfin EMAC Driver: the BF526 also supports the MAC, so updates things accordingly
Date: Wed, 27 Aug 2008 05:18:03 -0400 [thread overview]
Message-ID: <48B51BCB.60402@garzik.org> (raw)
In-Reply-To: <1219808877-15168-1-git-send-email-cooloney@kernel.org>
Bryan Wu wrote:
> From: Mike Frysinger <vapier.adi@gmail.com>
>
> Signed-off-by: Mike Frysinger <vapier.adi@gmail.com>
> Signed-off-by: Bryan Wu <cooloney@kernel.org>
> ---
> drivers/net/Kconfig | 6 +++---
> 1 files changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/net/Kconfig b/drivers/net/Kconfig
> index a5c141c..4a11296 100644
> --- a/drivers/net/Kconfig
> +++ b/drivers/net/Kconfig
> @@ -822,14 +822,14 @@ config ULTRA32
> will be called smc-ultra32.
>
> config BFIN_MAC
> - tristate "Blackfin 527/536/537 on-chip mac support"
> - depends on NET_ETHERNET && (BF527 || BF537 || BF536)
> + tristate "Blackfin on-chip MAC support"
> + depends on NET_ETHERNET && (BF526 || BF527 || BF536 || BF537)
> select CRC32
> select MII
> select PHYLIB
> select BFIN_MAC_USE_L1 if DMA_UNCACHED_NONE
> help
> - This is the driver for blackfin on-chip mac device. Say Y if you want it
> + This is the driver for Blackfin on-chip mac device. Say Y if you want it
> compiled into the kernel. This driver is also available as a module
> ( = code which can be inserted in and removed from the running kernel
> whenever you want). The module will be called bfin_mac.
applied
prev parent reply other threads:[~2008-08-27 9:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-27 3:47 [PATCH 1/1] netdev: Blackfin EMAC Driver: the BF526 also supports the MAC, so updates things accordingly Bryan Wu
2008-08-27 9:18 ` Jeff Garzik [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=48B51BCB.60402@garzik.org \
--to=jeff@garzik.org \
--cc=cooloney@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=vapier.adi@gmail.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.