From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: "Mike Miller (OS Dev)" <mikem@beardog.cca.cpqcorp.net>
Cc: LKML-SCSI <linux-scsi@vger.kernel.org>
Subject: Re: [RFC] hpsa: addressing review comments
Date: Fri, 13 Mar 2009 09:24:56 -0500 [thread overview]
Message-ID: <1236954296.3276.14.camel@localhost.localdomain> (raw)
In-Reply-To: <20090313142054.GB15269@beardog.cca.cpqcorp.net>
On Fri, 2009-03-13 at 09:20 -0500, Mike Miller (OS Dev) wrote:
> sorry, I fat fingered the address first time around...
>
> Date: Fri, 13 Mar 2009 09:18:49 -0500
> From: "Mike Miller (OS Dev)" <mikem@beardog.cca.cpqcorp.net>
> To: LKML <linux-kernel@vger.kernel.org>, lkml-scis@beardog.cca.cpqcorp.net
> Cc: Steve Cameron <scameron@beardog.cca.cpqcorp.net>, tom.lawler@hp.com,
> iss_storagedev@hp.com
> Subject: [RFC] hpsa: addressing review comments
>
> I have a question about the hpsa driver we recently released. We've received
> quite a few comments, very positive overall. When we make the changes noted,
> i.e., rip out /proc, style changes, etc., do we submit patches for that? Or
> repost the entire driver with the appropriate changelog?
Either is fine with me. Posting update patches is very useful to people
who want to see what changes have been made between versions. When we
iterate to a final version, then you can repost the whole thing (so it
can go into the tree as one to avoid bisection problems).
James
next prev parent reply other threads:[~2009-03-13 14:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-13 14:20 [RFC] hpsa: addressing review comments Mike Miller (OS Dev)
2009-03-13 14:24 ` James Bottomley [this message]
2009-03-13 18:35 ` Mike Miller (OS Dev)
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=1236954296.3276.14.camel@localhost.localdomain \
--to=james.bottomley@hansenpartnership.com \
--cc=linux-scsi@vger.kernel.org \
--cc=mikem@beardog.cca.cpqcorp.net \
/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