From: Alan Cox <alan@linux.intel.com>
To: Kirill Smelkov <kirr@mns.spb.ru>
Cc: linux-kernel@vger.kernel.org, Kirill Smelkov <kirr@mns.spb.ru>,
Jiri Slaby <jirislaby@gmail.com>,
Peter Botha <peterb@goldcircle.co.za>,
Denis Vlasenko <vda@ilport.com.ua>
Subject: Re: [RFC PATCH] mxser: make /dev/ttyMI<n> namespace contiguous
Date: Fri, 22 Jan 2010 11:40:37 +0000 [thread overview]
Message-ID: <20100122114037.06d073bf@linux.intel.com> (raw)
In-Reply-To: <1264161402-4669-1-git-send-email-kirr@mns.spb.ru>
> Maybe let's teach mxser to create continous /dev entries in the first
> place?
The existing mapping is ABI. Users do not expect their devices to
suddenly move around. If the driver hadn't been merged yet I'd not
object to the concept. However it is now years too late.
Remap it in userspace if you want, add udev rules for it if you like,
but the kernel mapping is set in stone.
Alan
next prev parent reply other threads:[~2010-01-22 12:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-22 11:56 [RFC PATCH] mxser: make /dev/ttyMI<n> namespace contiguous Kirill Smelkov
2010-01-22 11:40 ` Alan Cox [this message]
2010-01-25 8:05 ` Kirill Smelkov
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=20100122114037.06d073bf@linux.intel.com \
--to=alan@linux.intel.com \
--cc=jirislaby@gmail.com \
--cc=kirr@mns.spb.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=peterb@goldcircle.co.za \
--cc=vda@ilport.com.ua \
/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