public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@steeleye.com>
To: Andrew Vasquez <andrew.vasquez@qlogic.com>
Cc: SCSI Mailing List <linux-scsi@vger.kernel.org>
Subject: Re: [BKPATCH] Updated qla2xxx driver against scsi-misc-2.6.
Date: 30 Jan 2004 13:11:23 -0500	[thread overview]
Message-ID: <1075486284.2026.47.camel@mulgrave> (raw)
In-Reply-To: <B179AE41C1147041AA1121F44614F0B060EDFF@AVEXCH02.qlogic.org>

On Fri, 2004-01-30 at 11:59, Andrew Vasquez wrote:
> The bksend patch can be downloaded from the SF.net site:
> 
> 	http://prdownloads.sourceforge.net/linux-qla2xxx/qla2xxx-v2.6-20040130.bksend.bz2
> 
> I'm still trying to get the hang of using BK, so I hope sending updates
> in this way will be suitable.

Actually, not against my scsi-misc-2.6 tree, no.  The reason is that I
frequently take apart and rebuild that tree as the patch composition
changes (I did it only a day ago to pull out your initial SNS patch and
put the new one in).

BK is very fussy about having all changesets in a tree to do a bk
receive on.  However, as I pull apart the tree BK cannot import it
because the bkpatch now depends on missing changesets.

Using the tree internally to generate a real patch is fine, but I
frequently can't import bk patches against it.

> Here's the list of changes (1.1533 -> 1.1539) and a patch (1.1534 -> 
> 1.1539 -- minus the firmware file diffs [to reduce the noise]) for review.

I've successfully applied the diff in your email and added the history
to the single change set comment, thanks.

James



  reply	other threads:[~2004-01-30 18:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-30 16:59 [BKPATCH] Updated qla2xxx driver against scsi-misc-2.6 Andrew Vasquez
2004-01-30 18:11 ` James Bottomley [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-01-30 19:25 Andrew Vasquez

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=1075486284.2026.47.camel@mulgrave \
    --to=james.bottomley@steeleye.com \
    --cc=andrew.vasquez@qlogic.com \
    --cc=linux-scsi@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