Date: Thu, 8 Jan 2009 08:53:26 -0800
From: Greg KH <gregkh@suse.de>
To: Davide Rizzo <elpa.rizzo@gmail.com>
Cc: "Hans J. Koch" <hjk@linutronix.de>, linux-kernel@vger.kernel.org,
       ben-linux@fluff.org
Subject: Re: [PATCH 1/2] Driver for user access to internal timer
Message-ID: <20090108165326.GB13737@suse.de>
References: <8447d6730901080205o1a337d4cx867c7b2bd429ceb0@mail.gmail.com> <20090108112959.GB3053@local> <8447d6730901080337r190770d5s5eca64720bb7330f@mail.gmail.com> <20090108122524.GC3053@local> <8447d6730901080811pae17e75s75fc8f65f15a2675@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <8447d6730901080811pae17e75s75fc8f65f15a2675@mail.gmail.com>
User-Agent: Mutt/1.5.16 (2007-06-09)
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1101
Lines: 37

On Thu, Jan 08, 2009 at 05:11:20PM +0100, Davide Rizzo wrote:
> >> >
> >> > Davide,
> >> > please don't use drivers/uio/ for things that are no UIO drivers.
> >> >
> >> > Thanks,
> >> > Hans
> >>
> >> I thought drivers/uoi is a better choice then driver/misc, because
> >> this driver allows user to access internal hardware to generate PWM
> >> signals.
> >
> > Yes, but you do not use the UIO framework to achieve this.
> >
> >> Otherwise, where do you suggest to put it ?
> >
> > I didn't have a deeper look at your driver. I suggest you ask the people
> > who maintain the clock/timer frameworks you use. Since you seem to be
> > working on an ARM platform, you should Cc: the linux-arm-kernel mailing
> > list as well.
> >
> > Thanks,
> > Hans
> >
> >
> Moved to drivers/misc

But you are still using the "UIO_" config namespace :(

thanks,

greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/