From: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
linux-ide@vger.kernel.org,
Sergei Shtylyov <sshtylyov@ru.mvista.com>
Subject: Re: linux-next: Tree for February 12 (ide)
Date: Wed, 18 Feb 2009 19:58:18 +0100 [thread overview]
Message-ID: <200902181958.18733.bzolnier@gmail.com> (raw)
In-Reply-To: <499C42A8.7060003@oracle.com>
On Wednesday 18 February 2009, Randy Dunlap wrote:
> Bartlomiej Zolnierkiewicz wrote:
> > On Thursday 12 February 2009, Randy Dunlap wrote:
> >> Stephen Rothwell wrote:
> >>> Hi all,
> >>>
> >>> Changes since 20090211:
> >>
> >> When
> >> # CONFIG_BLK_DEV_IDEDMA is not set
> >>
> >> linux-next-20090212/drivers/ide/ide-taskfile.c:108: error: 'ide_dma_intr' undeclared (first use in this function)
> >
> > Thanks for spotting this, I fixed it in the revised patch:
>
> Hi Bart,
>
> Have you pushed this patch yet?
>
> linux-next (20090218) is still getting this IDE build error.
I got caught by some other things yesterday so this was pushed
out today. Sorry about confusion/delay.
Thanks,
Bart
next prev parent reply other threads:[~2009-02-18 18:58 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-12 8:44 linux-next: Tree for February 12 Stephen Rothwell
2009-02-12 10:42 ` next-20090212: drivers/watchdog/ks8695_wdt.c:68: error: 'CLOCK_TICK_RATE' undeclared (first use in this function) Alexey Dobriyan
2009-02-12 16:44 ` linux-next: Tree for February 12 (ide) Randy Dunlap
2009-02-17 14:19 ` Bartlomiej Zolnierkiewicz
2009-02-18 17:17 ` Randy Dunlap
2009-02-18 18:58 ` Bartlomiej Zolnierkiewicz [this message]
2009-02-12 17:38 ` [PATCH] wireless: fix for CONFIG_NL80211=n Randy Dunlap
2009-02-12 18:19 ` [PATCH -next] media/zoran: fix printk format Randy Dunlap
2009-02-12 18:43 ` [PATCH -next] x86_32: fix printk formats Randy Dunlap
2009-02-13 8:25 ` Ingo Molnar
2009-02-13 16:38 ` Randy Dunlap
2009-02-13 16:49 ` Jaswinder Singh Rajput
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=200902181958.18733.bzolnier@gmail.com \
--to=bzolnier@gmail.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=randy.dunlap@oracle.com \
--cc=sfr@canb.auug.org.au \
--cc=sshtylyov@ru.mvista.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.