From: Jeff Garzik <jeff@garzik.org>
To: akpm@linux-foundation.org
Cc: Tejun Heo <htejun@gmail.com>,
IDE/ATA development list <linux-ide@vger.kernel.org>
Subject: Re: + git-libata-all-fix.patch added to -mm tree
Date: Thu, 05 Jul 2007 20:58:21 -0400 [thread overview]
Message-ID: <468D93AD.3030409@garzik.org> (raw)
In-Reply-To: <200707060041.l660fX3C027811@imap1.linux-foundation.org>
akpm@linux-foundation.org wrote:
> The patch titled
> git-libata-all-fix
> has been added to the -mm tree. Its filename is
> git-libata-all-fix.patch
>
> *** Remember to use Documentation/SubmitChecklist when testing your code ***
>
> See http://www.zip.com.au/~akpm/linux/patches/stuff/added-to-mm.txt to find
> out what to do about this
>
> ------------------------------------------------------
> Subject: git-libata-all-fix
> From: Andrew Morton <akpm@linux-foundation.org>
>
> drivers/ata/libata-core.c:4253: error: redefinition of 'ata_fill_sg_dumb'
> drivers/ata/libata-core.c:4191: error: previous definition of 'ata_fill_sg_dumb' was here
> drivers/ata/libata-core.c:4375: error: redefinition of 'ata_dumb_qc_prep'
> drivers/ata/libata-core.c:4358: error: previous definition of 'ata_dumb_qc_prep' was here
>
> Cc: Jeff Garzik <jeff@garzik.org>
> Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
> ---
>
> drivers/ata/libata-core.c | 79 ------------------------------------
> 1 file changed, 79 deletions(-)
I think Tejun did something similar.
Alas, I only had time to concentrate on 2.6.22-rc before I left for July
4th. That left libata-dev.git in a minorly broken state, for everything
other than #master and #upstream-fixes. I should have that cleaned up
in the next day or so. My apologies.
Whee, bleeding edge...
Jeff
parent reply other threads:[~2007-07-06 0:58 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <200707060041.l660fX3C027811@imap1.linux-foundation.org>]
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=468D93AD.3030409@garzik.org \
--to=jeff@garzik.org \
--cc=akpm@linux-foundation.org \
--cc=htejun@gmail.com \
--cc=linux-ide@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).