All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dave C Boutcher <sleddog@us.ibm.com>
To: James Bottomley <James.Bottomley@SteelEye.com>
Cc: SCSI Mailing List <linux-scsi@vger.kernel.org>
Subject: Re: [patch] ibmvscsi.c: remove max-sectors module parm
Date: Fri, 31 Dec 2004 11:32:02 -0600	[thread overview]
Message-ID: <20041231173202.GA10809@cs.umn.edu> (raw)
In-Reply-To: <1104451489.7580.27.camel@mulgrave>

On Thu, Dec 30, 2004 at 06:04:48PM -0600, James Bottomley wrote:
> What I mean is that after there's been argument over a patch I want an
> updated diff (like the one below) with a new change log containing the
> resolution, not a diff to a previous patch.

OK, thanks for the guidance...new patch on its way.  I have a number
of subsequent patches which still apply fine (with some fuzz.)  Would
you like them resubmitted to get everything back in sync?

-- 
Dave Boutcher

      reply	other threads:[~2004-12-31 17:32 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-21 22:36 [patch] ibmvscsi.c: remove max-sectors module parm Dave C Boutcher
2004-12-23 19:03 ` James Bottomley
2004-12-23 20:01   ` Dave C Boutcher
2004-12-23 20:57     ` James Bottomley
2004-12-24  0:36       ` Dave C Boutcher
2004-12-31  0:04         ` James Bottomley
2004-12-31 17:32           ` Dave C Boutcher [this message]

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=20041231173202.GA10809@cs.umn.edu \
    --to=sleddog@us.ibm.com \
    --cc=James.Bottomley@SteelEye.com \
    --cc=boutcher@cs.umn.edu \
    --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 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.