From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: Stijn Tintel <stijn@linux-ipv6.be>
Cc: linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] MIPS: Octeon: add SNIC10E board
Date: Mon, 23 May 2022 11:17:21 +0200 [thread overview]
Message-ID: <20220523091721.GD5069@alpha.franken.de> (raw)
In-Reply-To: <20220518164810.2432678-1-stijn@linux-ipv6.be>
On Wed, May 18, 2022 at 07:48:10PM +0300, Stijn Tintel wrote:
> The CN6640-SNIC10E-G and CN6640-SNIC10E-1.1-G PCIe NICs are based on
> this board.
>
> Signed-off-by: Stijn Tintel <stijn@linux-ipv6.be>
> ---
> arch/mips/include/asm/octeon/cvmx-bootinfo.h | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/arch/mips/include/asm/octeon/cvmx-bootinfo.h b/arch/mips/include/asm/octeon/cvmx-bootinfo.h
> index 6c61e0a63924..c1c0b3230e0a 100644
> --- a/arch/mips/include/asm/octeon/cvmx-bootinfo.h
> +++ b/arch/mips/include/asm/octeon/cvmx-bootinfo.h
> @@ -253,6 +253,7 @@ enum cvmx_board_types_enum {
> CVMX_BOARD_TYPE_REDWING = 43,
> CVMX_BOARD_TYPE_NIC68_4 = 44,
> CVMX_BOARD_TYPE_NIC10E_66 = 45,
> + CVMX_BOARD_TYPE_SNIC10E = 50,
> CVMX_BOARD_TYPE_MAX,
>
> /*
> @@ -369,6 +370,7 @@ static inline const char *cvmx_board_type_to_string(enum
> ENUM_BRD_TYPE_CASE(CVMX_BOARD_TYPE_REDWING)
> ENUM_BRD_TYPE_CASE(CVMX_BOARD_TYPE_NIC68_4)
> ENUM_BRD_TYPE_CASE(CVMX_BOARD_TYPE_NIC10E_66)
> + ENUM_BRD_TYPE_CASE(CVMX_BOARD_TYPE_SNIC10E)
> ENUM_BRD_TYPE_CASE(CVMX_BOARD_TYPE_MAX)
>
> /* Customer boards listed here */
> --
> 2.35.1
applied to mips-next.
Thomas.
--
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea. [ RFC1925, 2.3 ]
prev parent reply other threads:[~2022-05-23 9:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-18 16:48 [PATCH] MIPS: Octeon: add SNIC10E board Stijn Tintel
2022-05-23 9:17 ` Thomas Bogendoerfer [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=20220523091721.GD5069@alpha.franken.de \
--to=tsbogend@alpha.franken.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=stijn@linux-ipv6.be \
/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).