From: Roland Dreier <rdreier@cisco.com>
To: James Bottomley <James.Bottomley@SteelEye.com>
Cc: linux-scsi@vger.kernel.org, openib-general@openib.org
Subject: Re: RFC: Add I/O class enum values to <scsi/srp.h>
Date: Mon, 05 Jun 2006 12:55:43 -0700 [thread overview]
Message-ID: <adafyijnzr4.fsf@cisco.com> (raw)
In-Reply-To: <1149536457.3479.2.camel@mulgrave.il.steeleye.com> (James Bottomley's message of "Mon, 05 Jun 2006 14:40:57 -0500")
James> No objection here ... but if you do, it will entangle our
James> git trees even more nastily, since the srp.h file is
James> created in the scsi-misc-2.6 tree.
No, I think we're OK. srp.h is already in Linus's tree (it went in as
part of the original IB SRP initiator merge), and scsi-misc doesn't have
any changes after ec448a0a36 (which is already upstream) in it. So
putting the IO Class change in my tree actually reduces the dependency
between our trees, since I can put the IB SRP changes in my tree
without worrying about you merging the srp.h change first.
- R.
prev parent reply other threads:[~2006-06-05 19:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-05 19:17 RFC: Add I/O class enum values to <scsi/srp.h> Roland Dreier
2006-06-05 19:40 ` James Bottomley
2006-06-05 19:55 ` Roland Dreier [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=adafyijnzr4.fsf@cisco.com \
--to=rdreier@cisco.com \
--cc=James.Bottomley@SteelEye.com \
--cc=linux-scsi@vger.kernel.org \
--cc=openib-general@openib.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.