From: Andrew Morton <akpm@osdl.org>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: torvalds@osdl.org, linux-kernel@vger.kernel.org, Robert.Picco@hp.com
Subject: Re: [PATCH] HPET driver
Date: Fri, 18 Jun 2004 14:55:31 -0700 [thread overview]
Message-ID: <20040618145531.015fbc12.akpm@osdl.org> (raw)
In-Reply-To: <40D35740.8070206@pobox.com>
Jeff Garzik <jgarzik@pobox.com> wrote:
>
> > [PATCH] HPET driver
> >
>
> Was this posted on lkml, or simply snuck in?
Was posted on lkml, was fairly widely reviewed, had comments from hch and
others, had several fixes from myself and from Robert and a long discussion
wrt the readq() implementation.
I'm not very happy with the driver, if only because its size and its prior
defect rate indicates that it probably has more problems. But it provides
support for new hardware which is being shipped in real products and we
need it. So ultimately one has to jam it into the tree in the hope that
doing so will get it a bit more attention.
> This should NOT have been merged without changes. Please fix ASAP, or
> revert and keep in -mm for a while.
Translation: Andrew has to personally understand and review every line
which goes into the kernel, unaided. Sorry, that doesn't work.
The patch was reviewed on lkml and has been in -mm for test and review for
five weeks. The initial reviews were not complete and sufficient attention
was not paid to it while it was in -mm.
To improve this process I need to find a way of provoking more attention
toward patches which I am not particularly confident about (and this one
certainly fell in that category). Thus far I've done that by merging them
into the main tree, which does work quite nicely. Perhaps I should send
these patches to lkml beforehand with big warning labels on them.
wrt the readq() implementation: I reverted the generic implementation based
on concerns raised on lkml by Eric Biederman. As a generic readq/writeq
implementation seems to be a new R&D project I decided to leave the
implementation private to the HPET driver until someone takes all of this
on.
wrt the hpets list locking: yeah, I noticed that, mentioned it to Robert
then forgot all about it. Mea Culpa.
wrt the request_irq() bug: yipes. Robert, please fix.
wrt the new miscdev minor: yes, devices.txt should be updated. When the
patch was first posted it was using a new major, but Robert changed that
based on review comments.
next prev parent reply other threads:[~2004-06-18 22:10 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200406181616.i5IGGECd003812@hera.kernel.org>
2004-06-18 20:57 ` Jeff Garzik
2004-06-18 21:55 ` Andrew Morton [this message]
2004-06-18 22:45 ` Jeff Garzik
2004-06-23 21:34 ` Robert Picco
2004-06-23 21:41 ` Jeff Garzik
2004-06-23 22:23 ` Andrew Morton
2004-05-13 22:34 Robert Picco
2004-05-13 23:17 ` Jeff Garzik
2004-05-13 23:42 ` Andrew Morton
2004-05-13 23:46 ` Andrew Morton
2004-05-13 23:49 ` Jeff Garzik
2004-05-14 11:19 ` Vojtech Pavlik
2004-05-14 16:59 ` Jeff Garzik
2004-05-17 22:33 ` Robert Picco
2004-05-17 22:39 ` Jeff Garzik
2004-05-17 22:43 ` Jeff Garzik
2004-05-17 23:05 ` Andrew Morton
2004-05-17 23:06 ` Jeff Garzik
2004-05-17 23:12 ` Andrew Morton
2004-05-17 23:18 ` Jeff Garzik
2004-05-17 23:25 ` Russell King
2004-05-17 23:41 ` Jeff Garzik
2004-05-17 23:33 ` Andrew Morton
2004-05-17 23:42 ` Jeff Garzik
2004-05-18 1:46 ` Andrew Morton
2004-05-18 1:59 ` Jeff Garzik
[not found] ` <16553.28862.590897.171478@napali.hpl.hp.com>
2004-05-20 2:01 ` Jeff Garzik
2004-05-13 23:18 ` Andrew Morton
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=20040618145531.015fbc12.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=Robert.Picco@hp.com \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.org \
/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
Powered by JetHome