From: Ben Dooks <ben-linux@fluff.org>
To: Simon Richter <Simon.Richter@hogyros.de>
Cc: Darius Augulis <augulis.darius@gmail.com>,
kgene.kim@samsung.com, Ben Dooks <ben-linux@fluff.org>,
paulius.zaleckas@gmail.com, linux-kernel@vger.kernel.org,
linux-serial@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [RESEND PATCH] serial: samsung: fix device name
Date: Mon, 27 Sep 2010 01:17:01 +0100 [thread overview]
Message-ID: <4C9FE27D.80407@fluff.org> (raw)
In-Reply-To: <20100924073453.GA3840@richter>
On 24/09/10 08:34, Simon Richter wrote:
> Hi,
>
> On Fri, Sep 24, 2010 at 09:57:19AM +0300, Darius Augulis wrote:
>
>> It does - now devices are named /dev/s3c2410_serial, and patch changes
>> its name to /dev/ttySAC
>
> I wonder if it'd make sense to name them ttyS[0-9]. I've never
> understood why the platform standard fixed serial ports on any device
> should have a different name.
Different driver. And yes, we've built systems with both this and
an 8250 base chip.
WARNING: multiple messages have this Message-ID (diff)
From: ben-linux@fluff.org (Ben Dooks)
To: linux-arm-kernel@lists.infradead.org
Subject: [RESEND PATCH] serial: samsung: fix device name
Date: Mon, 27 Sep 2010 01:17:01 +0100 [thread overview]
Message-ID: <4C9FE27D.80407@fluff.org> (raw)
In-Reply-To: <20100924073453.GA3840@richter>
On 24/09/10 08:34, Simon Richter wrote:
> Hi,
>
> On Fri, Sep 24, 2010 at 09:57:19AM +0300, Darius Augulis wrote:
>
>> It does - now devices are named /dev/s3c2410_serial, and patch changes
>> its name to /dev/ttySAC
>
> I wonder if it'd make sense to name them ttyS[0-9]. I've never
> understood why the platform standard fixed serial ports on any device
> should have a different name.
Different driver. And yes, we've built systems with both this and
an 8250 base chip.
next prev parent reply other threads:[~2010-09-27 0:17 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-23 19:15 [RESEND PATCH] serial: samsung: fix device name Darius Augulis
2010-09-23 19:15 ` Darius Augulis
2010-09-23 19:40 ` Wolfram Sang
2010-09-23 19:40 ` Wolfram Sang
2010-09-23 23:40 ` Ben Dooks
2010-09-23 23:40 ` Ben Dooks
2010-09-24 6:57 ` Darius Augulis
2010-09-24 6:57 ` Darius Augulis
2010-09-24 6:57 ` Darius Augulis
2010-09-24 7:34 ` Simon Richter
2010-09-24 7:34 ` Simon Richter
2010-09-24 7:34 ` Simon Richter
2010-09-24 7:42 ` Russell King - ARM Linux
2010-09-24 7:42 ` Russell King - ARM Linux
2010-09-27 0:17 ` Ben Dooks [this message]
2010-09-27 0:17 ` Ben Dooks
2010-09-24 16:37 ` Paulius Zaleckas
2010-09-24 16:37 ` Paulius Zaleckas
2010-09-24 16:37 ` Paulius Zaleckas
2010-09-27 0:18 ` Ben Dooks
2010-09-27 0:18 ` Ben Dooks
2010-09-27 8:20 ` Paulius Zaleckas
2010-09-27 8:20 ` Paulius Zaleckas
2010-09-27 8:20 ` Paulius Zaleckas
2010-09-27 8:24 ` Darius Augulis
2010-09-27 8:24 ` Darius Augulis
2010-09-27 8:24 ` Darius Augulis
2011-01-12 6:15 ` Kukjin Kim
2011-01-12 6:15 ` Kukjin Kim
2011-01-12 6:15 ` Kukjin Kim
2010-10-22 7:02 ` Darius Augulis
2010-10-22 7:02 ` Darius Augulis
2010-10-22 7:02 ` Darius Augulis
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=4C9FE27D.80407@fluff.org \
--to=ben-linux@fluff.org \
--cc=Simon.Richter@hogyros.de \
--cc=augulis.darius@gmail.com \
--cc=kgene.kim@samsung.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=paulius.zaleckas@gmail.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.