From: Russell King <rmk+lkml@arm.linux.org.uk>
To: Jeff Garzik <jeff@garzik.org>
Cc: Al Viro <viro@ftp.linux.org.uk>,
Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [git patches] IDE updates (part 2)
Date: Wed, 24 Oct 2007 14:12:43 +0100 [thread overview]
Message-ID: <20071024131243.GC32333@flint.arm.linux.org.uk> (raw)
In-Reply-To: <471F4035.4030507@garzik.org>
On Wed, Oct 24, 2007 at 08:53:09AM -0400, Jeff Garzik wrote:
> Russell King wrote:
> >On Mon, Oct 15, 2007 at 04:07:47PM -0400, Jeff Garzik wrote:
> >>Russell King wrote:
> >>>On Mon, Oct 15, 2007 at 03:54:16PM -0400, Jeff Garzik wrote:
> >>>>Al Viro wrote:
> >>>>>Proposed addition to icside part, provided that ARM folks ACK it - gets
> >>>>>icside to build and AFAICS it's correct:
> >>>>ACK from me too... ARM folks?
> >>>Will test tomorrow/Wednesday.
> >>Thanks. Sorry about missing your CC on the libata-wide ata_link
> >>changes. We should have poked the maintainers on that, for the drivers
> >>we cannot build ourselves.
> >
> >I think Viro's patch got an ack from everyone. Who's dealing with getting
> >this regression fix into mainline? It seems at the moment the patch is in
> >limbo.
>
> I was waiting on you, who last said "Will test tomorrow/Wednesday" (with
> presumably an ACK forthcoming after test results)
>
> If it now has your ACK, it's ready and waiting in my mbox queue to be
> merged upstream.
Looks like it got my ack more than a week ago:
| Date: Tue, 16 Oct 2007 16:55:07 +0100
| From: Russell King <rmk+lkml@arm.linux.org.uk>
| To: Al Viro <viro@ftp.linux.org.uk>
| Cc: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>,
| Linus Torvalds <torvalds@linux-foundation.org>,
| linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org
| Subject: Re: [git patches] IDE updates (part 2)
|
| On Sun, Oct 14, 2007 at 01:12:39AM +0100, Al Viro wrote:
| > Proposed addition to icside part, provided that ARM folks ACK it - gets
| > icside to build and AFAICS it's correct:
|
| Booted and tested as working.
|
| Whatever-tag-that-is: Russell King <rmk+kernel@arm.linux.org.uk>
which I gave to the _initial_ message asking for my ack. And no, before
you whinge and moan, I didn't drop any CC's.
--
Russell King
Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/
maintainer of:
next prev parent reply other threads:[~2007-10-24 13:17 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-13 16:25 [git patches] IDE updates (part 2) Bartlomiej Zolnierkiewicz
2007-10-13 19:56 ` Alan Cox
2007-10-13 20:59 ` Bartlomiej Zolnierkiewicz
2007-10-13 21:44 ` Alan Cox
2007-10-13 22:09 ` Bartlomiej Zolnierkiewicz
2007-10-13 22:29 ` Alan Cox
2007-10-13 22:41 ` Bartlomiej Zolnierkiewicz
2007-10-14 0:08 ` Benjamin Herrenschmidt
2007-10-14 16:07 ` Bartlomiej Zolnierkiewicz
2007-10-14 21:15 ` Benjamin Herrenschmidt
2007-10-16 19:41 ` Bartlomiej Zolnierkiewicz
2007-10-14 0:12 ` Al Viro
2007-10-14 16:21 ` Bartlomiej Zolnierkiewicz
2007-10-15 19:54 ` Jeff Garzik
2007-10-15 19:58 ` Russell King
2007-10-15 20:07 ` Jeff Garzik
2007-10-24 12:38 ` Russell King
2007-10-24 12:53 ` Jeff Garzik
2007-10-24 13:12 ` Russell King [this message]
2007-10-24 13:20 ` Jeff Garzik
2007-10-16 15:55 ` Russell King
2007-10-25 6:05 ` Jeff Garzik
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=20071024131243.GC32333@flint.arm.linux.org.uk \
--to=rmk+lkml@arm.linux.org.uk \
--cc=bzolnier@gmail.com \
--cc=jeff@garzik.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=viro@ftp.linux.org.uk \
/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).