All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jeff@garzik.org>
To: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
Cc: linux-ide@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
	David Miller <davem@davemloft.net>
Subject: Re: What's in libata-dev.git?
Date: Thu, 03 Dec 2009 14:40:38 -0500	[thread overview]
Message-ID: <4B181436.90008@garzik.org> (raw)
In-Reply-To: <200912032020.16608.bzolnier@gmail.com>

On 12/03/2009 02:20 PM, Bartlomiej Zolnierkiewicz wrote:
> On Thursday 03 December 2009 08:14:12 pm Jeff Garzik wrote:
>> On 12/03/2009 10:47 AM, Bartlomiej Zolnierkiewicz wrote:
>>> ( Jeff, you probably would want to take ide-pci-generic fix to your tree
>>>     as libata-dev tree currently breaks build for IDE tree. )
>>
>> I didn't know that.
>
> You would know if you would be either:
>
> 	a) reading
>
> or
>
> 	b) building
>
> patches that you're applying.

Strange that I do both.

But still...  <looks>  ah, I had disabled the *generic drivers in the 
kernel build, and missed a missing comma.  Fixed and rebased #upstream.

	Jeff




  reply	other threads:[~2009-12-03 19:40 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-03  7:56 What's in libata-dev.git? Jeff Garzik
2009-12-03 15:47 ` Bartlomiej Zolnierkiewicz
2009-12-03 19:14   ` Jeff Garzik
2009-12-03 19:20     ` Bartlomiej Zolnierkiewicz
2009-12-03 19:40       ` Jeff Garzik [this message]
2009-12-03 23:08 ` What's in libata-dev.git? (v2) Jeff Garzik
  -- strict thread matches above, loose matches on Subject: below --
2009-09-11  6:42 What's in libata-dev.git? Jeff Garzik
2009-09-13  7:01 ` Robert Hancock
2007-09-08 17:41 Jeff Garzik
2007-04-17 17:04 Jeff Garzik
2007-04-17 17:08 ` 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=4B181436.90008@garzik.org \
    --to=jeff@garzik.org \
    --cc=bzolnier@gmail.com \
    --cc=davem@davemloft.net \
    --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 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.