From: Roland Dreier <rdreier@cisco.com>
To: Mike Christie <michaelc@cs.wisc.edu>
Cc: Or Gerlitz <ogerlitz@voltaire.com>,
openib-general@openib.org, linux-scsi@vger.kernel.org
Subject: Re: [PATCH] IB/iser: do I/O path allocations with GFP_NOIO
Date: Tue, 30 May 2006 13:35:37 -0700 [thread overview]
Message-ID: <ada64jn6yjq.fsf@cisco.com> (raw)
In-Reply-To: <447CA214.7010202@cs.wisc.edu> (Mike Christie's message of "Tue, 30 May 2006 14:50:44 -0500")
Mike> Should iser patches have linux-scsi ccd on them in the
Mike> future? And should they go through the scsi maintainer
Mike> normally (I understand they cannot now since James does not
Mike> have all the infinniband bits)? I am really just trying to
Mike> avoid any coordinatation issues that come about by having
Mike> core iscsi and tcp iscsi patched sent to the scsi maintainer
Mike> then having to have iser going through Roland.
Mike> Does srp go from openib-general and Roland then to lkml? For
Mike> iscsi we do not go through net-dev and we live in
Mike> drivers/scsi so maybe we are the odd driver?:) What is the
Mike> proper or normal procedure?
It's a problem because SRP and iSER are straddling both the SCSI and
IB worlds. Probably the best policy is to cc all relevant mailing
lists (at least linux-scsi and openib-general) whenever there's a
doubt about who should see something.
As far as merging patches goes, I've been merging SRP changes directly
to Linus, except for generic fixes to <scsi/srp.h>, which I've been
sending through James. Or felt that iSCSI should be merged through my
tree, but I have no problem if in the future patches bypass my tree.
(But I would like to be cc'ed on changes to IB stuff, especially core
things outside of specific drivers)
(Which all reminds me I have a question about SCSI EH and SRP to send
to the linux-scsi list...)
- R.
next prev parent reply other threads:[~2006-05-30 20:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.64.0605301448001.734@zuben>
2006-05-30 19:50 ` [PATCH] IB/iser: do I/O path allocations with GFP_NOIO Mike Christie
2006-05-30 20:35 ` Roland Dreier [this message]
2006-05-31 12:55 ` Or Gerlitz
2006-05-31 14:29 ` FUJITA Tomonori
2006-05-31 14:41 ` Roland Dreier
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=ada64jn6yjq.fsf@cisco.com \
--to=rdreier@cisco.com \
--cc=linux-scsi@vger.kernel.org \
--cc=michaelc@cs.wisc.edu \
--cc=ogerlitz@voltaire.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).