From: gregory.clement@bootlin.com (Gregory CLEMENT)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/2] ARM: mvebu_v7_defconfig: enable SFP support
Date: Thu, 28 Jun 2018 14:07:47 +0200 [thread overview]
Message-ID: <87fu176rn0.fsf@bootlin.com> (raw)
In-Reply-To: <b130ccb8a9812530d33a71afb1563545fa8808cf.1530169575.git.baruch@tkos.co.il> (Baruch Siach's message of "Thu, 28 Jun 2018 10:06:15 +0300")
Hi Baruch,
On jeu., juin 28 2018, Baruch Siach <baruch@tkos.co.il> wrote:
> This enables support for SFP cages on SolidRun Armada 38x and 8k
> platforms.
>
> Signed-off-by: Baruch Siach <baruch@tkos.co.il>
Applied on mvebu/arm
Thanks,
Gregory
> ---
> arch/arm/configs/mvebu_v7_defconfig | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/arch/arm/configs/mvebu_v7_defconfig b/arch/arm/configs/mvebu_v7_defconfig
> index 1ff371ae688d..55140219ab11 100644
> --- a/arch/arm/configs/mvebu_v7_defconfig
> +++ b/arch/arm/configs/mvebu_v7_defconfig
> @@ -66,6 +66,7 @@ CONFIG_NETDEVICES=y
> CONFIG_MV643XX_ETH=y
> CONFIG_MVNETA=y
> CONFIG_MVPP2=y
> +CONFIG_SFP=y
> CONFIG_MARVELL_PHY=y
> CONFIG_MWIFIEX=y
> CONFIG_MWIFIEX_SDIO=y
> --
> 2.18.0
>
--
Gregory Clement, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
http://bootlin.com
next prev parent reply other threads:[~2018-06-28 12:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-28 7:06 [PATCH 1/2] ARM: mvebu_v7_defconfig: sync defconfig Baruch Siach
2018-06-28 7:06 ` [PATCH 2/2] ARM: mvebu_v7_defconfig: enable SFP support Baruch Siach
2018-06-28 12:07 ` Gregory CLEMENT [this message]
2018-06-28 13:14 ` Thomas Petazzoni
2018-06-28 14:44 ` Baruch Siach
2018-06-28 14:53 ` Gregory CLEMENT
2018-06-28 12:05 ` [PATCH 1/2] ARM: mvebu_v7_defconfig: sync defconfig Gregory CLEMENT
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=87fu176rn0.fsf@bootlin.com \
--to=gregory.clement@bootlin.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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).