From: Luben Tuikov <luben_tuikov@adaptec.com>
To: arjanv@redhat.com
Cc: Nathan Bryant <nbryant@optonline.net>,
Sam Ravnborg <sam@ravnborg.org>,
"Justin T. Gibbs" <gibbs@scsiguy.com>,
Adrian Bunk <bunk@fs.tum.de>,
James.Bottomley@HansenPartnership.com,
linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [2.6 patch] let AIC7{9,X}XX_BUILD_FIRMWARE depend on!PREVENT_FIRMWARE_BUILD
Date: Tue, 03 Aug 2004 13:49:41 -0400 [thread overview]
Message-ID: <410FD035.6080905@adaptec.com> (raw)
In-Reply-To: <1091550985.2816.10.camel@laptop.fenrus.com>
Arjan van de Ven wrote:
> On Tue, 2004-08-03 at 18:30, Nathan Bryant wrote:
>
>>Luben Tuikov wrote:
>>
>>>Hi Sam,
>>>
>>>You can forward it to Linus and I'll also integrate it
>>>to the latest version of the drivers, yet to be integrated
>>>to the mainline kernel.
>>
>>Luben -
>>
>>Are the latest drivers going to be available in BitKeeper format before
>>they get merged?
>
>
> I'm sure they'll be submitted in small incremental updates which can be
> submitted and merged in smaller pieces to keep testability to a
> maximum....
Yes, no problem. Whatever you guys want.
I can provide small incremental patches (right out of
perforce), and generate incremantal BKs (will have to look into
that).
--
Luben
next prev parent reply other threads:[~2004-08-03 17:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-01 18:55 [2.6 patch] let AIC7{9,X}XX_BUILD_FIRMWARE depend on !PREVENT_FIRMWARE_BUILD Adrian Bunk
2004-08-01 19:11 ` Sam Ravnborg
2004-08-01 19:11 ` Sam Ravnborg
2004-08-01 19:16 ` Justin T. Gibbs
2004-08-03 14:47 ` Luben Tuikov
2004-08-03 16:30 ` Nathan Bryant
2004-08-03 16:36 ` Arjan van de Ven
2004-08-03 17:49 ` Luben Tuikov [this message]
2004-08-03 19:31 ` [2.6 patch] let AIC7{9,X}XX_BUILD_FIRMWARE depend on!PREVENT_FIRMWARE_BUILD James Bottomley
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=410FD035.6080905@adaptec.com \
--to=luben_tuikov@adaptec.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=arjanv@redhat.com \
--cc=bunk@fs.tum.de \
--cc=gibbs@scsiguy.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=nbryant@optonline.net \
--cc=sam@ravnborg.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.