From: Andrew Lunn <andrew@lunn.ch>
To: Chris Healy <cphealy@gmail.com>
Cc: Andrey Smirnov <andrew.smirnov@gmail.com>,
Shawn Guo <shawnguo@kernel.org>,
devicetree@vger.kernel.org,
linux-kernel <linux-kernel@vger.kernel.org>,
Fabio Estevam <fabio.estevam@nxp.com>,
linux ARM <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] ARM: dts: vf610: Add ZII SSMB SPU3 board
Date: Tue, 17 Jul 2018 17:20:35 +0200 [thread overview]
Message-ID: <20180717152035.GD16320@lunn.ch> (raw)
In-Reply-To: <CAFXsbZpKyLjp0bO7MVR5StKf=3UkXUANydhM+8_13G3itRmE+Q@mail.gmail.com>
> >> +++ b/arch/arm/boot/dts/vf610-zii-ssmb-spu3.dts
> >> @@ -0,0 +1,343 @@
> >> +// SPDX-License-Identifier: (GPL-2.0 OR MIT)
> >> +
> >> +/*
> >> + * Device tree file for ZII's SSMB SPU3 board
> >> + *
> >> + * SSMB - SPU3 Switch Management Board
> >> + * SPU - Seat Power Unit
> >
> > I think this is the first Zodiac board with mutually recursive
> > acronyms.
> >
> > Probably a question for Chris: Does SSMB specifically refer to version
> > 3 of the SPU?
> >
> > Andrew
>
> SPU3 is the third generation of seat power unit.
> SSMB is the SPU3 Switch Management Board.
>
> So, SSMB is a backronym. This naming scheme breaks down a bit though
> when follow on designs (that are not the SPU3) also use the SSMB, but
> that's what it is... ;-)
O.K, i was just wondering if the 3 was in the wrong place. More
logically, it would be
* SSMB - SPU Switch Management Board
* SPU 3 - Seat Power Unit, version 3.
But you are saying the Marketing guys messed up the naming and
engineering is now stuck with it.
Andrew
next prev parent reply other threads:[~2018-07-17 15:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-17 4:06 [PATCH] ARM: dts: vf610: Add ZII SSMB SPU3 board Andrey Smirnov
2018-07-17 14:46 ` Andrew Lunn
2018-07-17 14:55 ` Chris Healy
2018-07-17 15:20 ` Andrew Lunn [this message]
2018-07-17 15:22 ` Chris Healy
2018-07-17 15:08 ` Chris Healy
2018-07-18 22:50 ` Fabio Estevam
2018-07-19 0:51 ` Andrey Smirnov
2018-07-19 0:52 ` Fabio Estevam
2018-07-19 2:40 ` Shawn Guo
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=20180717152035.GD16320@lunn.ch \
--to=andrew@lunn.ch \
--cc=andrew.smirnov@gmail.com \
--cc=cphealy@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=fabio.estevam@nxp.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=shawnguo@kernel.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).