From: David Miller <davem@davemloft.net>
To: bzolnier@gmail.com
Cc: linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [patch 4/6] ide: allow ide_dev_read_id() to be called from the IRQ context
Date: Fri, 07 Aug 2009 10:36:10 -0700 (PDT) [thread overview]
Message-ID: <20090807.103610.209136140.davem@davemloft.net> (raw)
In-Reply-To: <200908071927.36367.bzolnier@gmail.com>
From: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
Date: Fri, 7 Aug 2009 19:27:36 +0200
> Are you trying to tell me that after 6 weeks there is still no public
> tree to hold future IDE changes?
>
> If this is indeed a case here I hope that it will get addressed ASAP.
IDE is deep maintainence, we shouldn't be doing lots of changes,
cleanups, and things of this nature. So urgency and timeliness
is on a sincerely different scale for it.
On the other hand, if you've been looking, I've been applying
networking patches to net-2.6 and net-next-2.6 by the truckload
on a daily basis because it is in active development.
next prev parent reply other threads:[~2009-08-07 17:36 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-23 21:29 [patch 4/6] ide: allow ide_dev_read_id() to be called from the IRQ context Bartlomiej Zolnierkiewicz
2009-06-23 23:22 ` David Miller
2009-06-24 1:36 ` Bartlomiej Zolnierkiewicz
2009-06-24 4:35 ` David Miller
2009-06-24 9:51 ` Bartlomiej Zolnierkiewicz
2009-06-24 9:55 ` David Miller
2009-06-24 10:48 ` Bartlomiej Zolnierkiewicz
2009-06-24 11:04 ` Bartlomiej Zolnierkiewicz
2009-06-24 13:05 ` Bartlomiej Zolnierkiewicz
2009-06-24 19:30 ` Jeff Garzik
2009-06-24 19:55 ` Bartlomiej Zolnierkiewicz
2009-07-01 16:35 ` Bartlomiej Zolnierkiewicz
2009-07-01 20:47 ` David Miller
2009-08-07 11:55 ` Bartlomiej Zolnierkiewicz
2009-08-07 16:01 ` David Miller
2009-08-07 17:27 ` Bartlomiej Zolnierkiewicz
2009-08-07 17:36 ` David Miller [this message]
2009-08-07 17:46 ` Bartlomiej Zolnierkiewicz
2009-08-07 18:09 ` David Miller
2009-08-07 18:35 ` Bartlomiej Zolnierkiewicz
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=20090807.103610.209136140.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=bzolnier@gmail.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).