From: Pavel Machek <pavel@ucw.cz>
To: Sowmini Varadhan <sowmini.varadhan@oracle.com>,
arnd@arndb.de, gthelen@google.com, jgg@mellanox.com
Cc: santosh.shilimkar@oracle.com,
kernel list <linux-kernel@vger.kernel.org>,
Netdev list <netdev@vger.kernel.org>
Subject: Re: [PATCH] RDS is not Radio Data System
Date: Sun, 5 Aug 2018 12:37:56 +0200 [thread overview]
Message-ID: <20180805103756.GA24849@amd> (raw)
In-Reply-To: <20180805101945.GA4056@oracle.com>
[-- Attachment #1: Type: text/plain, Size: 1306 bytes --]
On Sun 2018-08-05 06:19:45, Sowmini Varadhan wrote:
> On (08/05/18 08:59), Pavel Machek wrote:
> > Getting prompt "The RDS Protocol" (RDS) is not too helpful, and it is
> > easily confused with Radio Data System (which we may want to support
> > in kernel, too).
> >
> > I wonder if option should be named NET_RDS, instead?
>
> RDS has been around for a while now (since 2.6). How will you
> rename proposal manage backward compatibility? Why can't you call
> your new option CONFIG_RADIO or similar instead?
>
> Are we going to rename NFS* to NET_NFS* because someone decided
> to reuse the NFS acronym?
Was it?
Because this was first time kernel asked that question... when I was
testing -next. Is this related?
commit 533d1daea8d8a389b37207ad7b50c4e750969231
IB: Revert "remove redundant INFINIBAND kconfig dependencies"
> > And this sounds like a good idea:
> > - tristate "The RDS Protocol"
> > + tristate "The Reliable Datagram Sockets (RDS) Protocol"
>
> surn that sounds fine.
Can you apply the patch, or do you want me to send it to davem?
Signed-off-by: Pavel Machek <pavel@ucw.cz>
Thanks,
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
next prev parent reply other threads:[~2018-08-05 10:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-05 6:59 [PATCH] RDS is not Radio Data System Pavel Machek
2018-08-05 10:19 ` Sowmini Varadhan
2018-08-05 10:37 ` Pavel Machek [this message]
2018-08-05 11:24 ` Sowmini Varadhan
2018-08-06 3:41 ` santosh.shilimkar
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=20180805103756.GA24849@amd \
--to=pavel@ucw.cz \
--cc=arnd@arndb.de \
--cc=gthelen@google.com \
--cc=jgg@mellanox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=santosh.shilimkar@oracle.com \
--cc=sowmini.varadhan@oracle.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.