From: Mark Jackson <mpfj-list@newflow.co.uk>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Lucas De Marchi <lucas.de.marchi@gmail.com>,
Haavard Skinnemoen <haavard.skinnemoen@atmel.com>
Cc: kay.sievers@vrfy.org, linux-kernel@vger.kernel.org,
Rob Landley <rob@landley.net>,
Lucas De Marchi <lucas.demarchi@intel.com>
Subject: Re: [PATCH 2/2] misc: add missing minor nodes
Date: Wed, 19 Feb 2014 19:46:02 +0000 [thread overview]
Message-ID: <530509FA.9070800@newflow.co.uk> (raw)
In-Reply-To: <20140218185228.GC29209@kroah.com>
On 18/02/14 18:52, Greg Kroah-Hartman wrote:
> On Tue, Feb 18, 2014 at 02:27:25AM -0300, Lucas De Marchi wrote:
>> From: Lucas De Marchi <lucas.demarchi@intel.com>
>>
>> Signed-off-by: Lucas De Marchi <lucas.demarchi@intel.com>
>> ---
>> Documentation/devices.txt | 3 +++
>> 1 file changed, 3 insertions(+)
>>
>> diff --git a/Documentation/devices.txt b/Documentation/devices.txt
>> index 04356f5..0ea1cc2 100644
>> --- a/Documentation/devices.txt
>> +++ b/Documentation/devices.txt
>> @@ -329,6 +329,7 @@ Your cooperation is appreciated.
>> filesystem across multiple physical disks.
>>
>> 10 char Non-serial mice, misc features
>> + 0 = /dev/fram
>> 0 = /dev/logibm Logitech bus mouse
>> 1 = /dev/psaux PS/2-style mouse port
>> 2 = /dev/inportbm Microsoft Inport bus mouse
>
> That's not ok at all, and probably a bug, someone must have thought that
> minor 0 ment "give me a dynamic number." No one caught this when the
> driver was first merged in a arch-specific tree in 2008 :(
>
> In looking at the driver, it probably should just be a UIO driver, or
> something else, all it does it map frame buffer memory to userspace,
> given the hardware involved, odds are no one even uses it anymore...
>
> Mark and Haavard, any thoughts about the
> arch/avr32/boards/mimc200/fram.c driver? Can I fix up the minor number
> here, or just delete the driver entirely if it's not being used anymore?
I think it's safe to delete the driver.
The mimc200 unit is now basically obsolete and there'll be no new development on it.
Regards
Mark J.
next prev parent reply other threads:[~2014-02-19 20:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-18 5:27 [PATCH 0/2] Fix missing misc nodes Lucas De Marchi
2014-02-18 5:27 ` [PATCH 1/2] misc: add comment on unused minors Lucas De Marchi
2014-02-18 5:27 ` [PATCH 2/2] misc: add missing minor nodes Lucas De Marchi
2014-02-18 18:52 ` Greg Kroah-Hartman
2014-02-19 19:46 ` Mark Jackson [this message]
2014-02-19 21:17 ` Lucas De Marchi
2014-02-18 18:53 ` [PATCH 0/2] Fix missing misc nodes Greg Kroah-Hartman
2014-02-19 1:56 ` Valdis.Kletnieks
2014-02-19 11:45 ` One Thousand Gnomes
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=530509FA.9070800@newflow.co.uk \
--to=mpfj-list@newflow.co.uk \
--cc=gregkh@linuxfoundation.org \
--cc=haavard.skinnemoen@atmel.com \
--cc=kay.sievers@vrfy.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lucas.de.marchi@gmail.com \
--cc=lucas.demarchi@intel.com \
--cc=rob@landley.net \
/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