From: Johan Hovold <johan@kernel.org>
To: Pavel Machek <pavel@ucw.cz>
Cc: Randy Dunlap <rdunlap@infradead.org>,
linux-kernel@vger.kernel.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Re: [PATCH] gnss: tell what GNSS means
Date: Mon, 30 Oct 2023 11:10:17 +0100 [thread overview]
Message-ID: <ZT-BCS_tGfbeYQyL@hovoldconsulting.com> (raw)
In-Reply-To: <ZT4GnZUUVy0Ri5rS@duo.ucw.cz>
[-- Attachment #1: Type: text/plain, Size: 1125 bytes --]
On Sun, Oct 29, 2023 at 08:15:41AM +0100, Pavel Machek wrote:
> On Mon 2023-10-16 16:38:28, Johan Hovold wrote:
> > On Sun, Sep 24, 2023 at 10:43:46PM -0700, Randy Dunlap wrote:
> > > Tell users what GNSS means in the Kconfig prompt.
> >
> > > menuconfig GNSS
> > > - tristate "GNSS receiver support"
> > > + tristate "GNSS (Global Navigation Satellite System) receiver support"
> >
> > No, I don't like the way this clutters menuconfig. The above would make
> > this one of the longest entries and for very little gain.
>
> Yeah, because everyone knows what GNSS means.
It's an established term (e.g. see [1]), and as I mentioned in the
context you dropped we don't spell out what NVMe or SPI stands for
either.
> Except that most people know GNSS as GPS. You misnamed the subsystem,
> so it now needs explanation :-(.
No, naming it GPS would have been too specific as these receivers are
not just for GPS.
Either way, this is about not cluttering up menuconfig and making that
harder to navigate for no good reason.
Johan
[1] https://www.u-blox.com/en/positioning-chips-and-modules
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
prev parent reply other threads:[~2023-10-30 10:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-25 5:43 Randy Dunlap
2023-10-16 14:38 ` Johan Hovold
2023-10-29 7:15 ` Pavel Machek
2023-10-29 12:13 ` Randy Dunlap
2023-10-30 10:10 ` Johan Hovold [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=ZT-BCS_tGfbeYQyL@hovoldconsulting.com \
--to=johan@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=rdunlap@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
all inboxes | Powered by JetHome®