From: Or Gerlitz <ogerlitz@voltaire.com>
To: Mike Christie <michaelc@cs.wisc.edu>
Cc: Roland Dreier <rdreier@cisco.com>,
openib-general@openib.org, linux-scsi@vger.kernel.org
Subject: Re: [PATCH] IB/iser: do I/O path allocations with GFP_NOIO
Date: Wed, 31 May 2006 15:55:28 +0300 [thread overview]
Message-ID: <447D9240.3010106@voltaire.com> (raw)
In-Reply-To: <ada64jn6yjq.fsf@cisco.com>
Roland Dreier wrote:
> 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.
We are monitoring linux-scsi for tracking iscsi upstream updates.
> 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)
At this point, we prefer that iser related updates/merges would go
through Roland, the IB maintainer, if this poses a problem for
scsi/iscsi updates we are open to send our updates/merges via the scsi
maintainer.
Or.
next prev parent reply other threads:[~2006-05-31 12:55 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
2006-05-31 12:55 ` Or Gerlitz [this message]
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=447D9240.3010106@voltaire.com \
--to=ogerlitz@voltaire.com \
--cc=linux-scsi@vger.kernel.org \
--cc=michaelc@cs.wisc.edu \
--cc=openib-general@openib.org \
--cc=rdreier@cisco.com \
/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.