From: Paul Mundt <lethal@linux-sh.org>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Andrew Morton <akpm@osdl.org>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
linux-kernel@vger.kernel.org, Greg KH <greg@kroah.com>
Subject: Re: Industrial device driver uio/uio_*
Date: Thu, 5 Oct 2006 17:12:47 +0900 [thread overview]
Message-ID: <20061005081247.GA8218@localhost.hsdv.com> (raw)
In-Reply-To: <1159990345.1386.277.camel@localhost.localdomain>
On Wed, Oct 04, 2006 at 09:32:25PM +0200, Thomas Gleixner wrote:
> On Wed, 2006-10-04 at 12:18 -0700, Andrew Morton wrote:
> > On Wed, 04 Oct 2006 19:59:54 +0100
> > > I would just NAK it but want to be sure the guys saw the list of
> > > problems
> > >
> >
> > cc's added.
> >
> > Thomas has been a bit tied up with timers and interrupts of late.
>
> Yup. fork(tglx) still returns -ETOOMANYINSTANCES.
>
> I have no objections, if you pull it from -mm for now. The list of flaws
> is accepted and we'll work on this in foreseeable time, _IF_ there is
> some basic consensus about the idea itself not being fundamentaly wrong.
>
I've got a few cycles I can throw at this, it's a problem space we
(Renesas) are interested in too..
Alan, is your Sept. 11 list the extent of your issues with the current
code, or was there more that you sent off-list?
I'll toss up a quick git tree for this so we don't lose anything, and
the fixes can trickle in to -mm that way, or it can just be pulled and
added back later.
next prev parent reply other threads:[~2006-10-05 8:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-11 17:22 Industrial device driver uio/uio_* Alan Cox
2006-09-11 19:23 ` Jan Engelhardt
2006-09-12 1:43 ` Greg KH
2006-09-17 9:41 ` Jan Engelhardt
2006-10-04 18:59 ` Alan Cox
2006-10-04 19:18 ` Andrew Morton
2006-10-04 19:32 ` Thomas Gleixner
2006-10-04 21:37 ` Alan Cox
2006-10-05 8:12 ` Paul Mundt [this message]
2006-10-05 12:12 ` Alan Cox
2006-10-06 0:37 ` Greg KH
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=20061005081247.GA8218@localhost.hsdv.com \
--to=lethal@linux-sh.org \
--cc=akpm@osdl.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
/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