mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Dmitry Torokhov" <dmitry.torokhov@gmail.com>
To: "Paul Mundt" <lethal@linux-sh.org>,
	"Kristoffer Ericson" <kristoffer.ericson@gmail.com>,
	Dmitry <dmitry.torokhov@gmail.com>,
	"Russell King" <linux@arm.linux.org.uk>,
	linux-main <linux-kernel@vger.kernel.org>
Subject: Re: Question regarding naming scheme (HP Jornada 6XX/7XX)
Date: Mon, 26 Nov 2007 09:40:14 -0500	[thread overview]
Message-ID: <d120d5000711260640y68c6136fy181b63af85bf6ae6@mail.gmail.com> (raw)
In-Reply-To: <20071126043030.GA25664@linux-sh.org>

On Nov 25, 2007 11:30 PM, Paul Mundt <lethal@linux-sh.org> wrote:
> On Mon, Nov 26, 2007 at 12:03:29AM +0100, Kristoffer Ericson wrote:
>
> > Why I want to use 600-series/700-series instead of 6XX/7XX is simply
> > because 600-series/700-series leaves no doubt.
> >
> Apparently your end users are more technically apt than I am, as I have
> no idea how using 00 over XX makes things any less ambiguous.
>
> We already have a 6xx mach-type that drivers can set their dependency on.
> If it's not 680-only, then that's a perfectly reasonable dependency. Feel
> free to change the Kconfig text to make the description more useful, but
> please don't start idly shuffling around code and symbols because users
> can't work out why a driver is available that they can't support.

Agreed. Users simply should not care what a particular module is
called. If Kconfig entries and/or its help is unclear on whta devices
are supported by the drivers let's fix that.

-- 
Dmitry

  reply	other threads:[~2007-11-26 14:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-25 23:03 Kristoffer Ericson
2007-11-26  4:30 ` Paul Mundt
2007-11-26 14:40   ` Dmitry Torokhov [this message]
2007-11-26 16:53     ` Kristoffer Ericson

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=d120d5000711260640y68c6136fy181b63af85bf6ae6@mail.gmail.com \
    --to=dmitry.torokhov@gmail.com \
    --cc=kristoffer.ericson@gmail.com \
    --cc=lethal@linux-sh.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    /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®