From: Christoph Hellwig <hch@infradead.org>
To: Neil Horman <nhorman@tuxdriver.com>
Cc: Vasu Dev <vasu.dev@linux.intel.com>,
fcoe-devel@open-fcoe.org, linux-scsi@vger.kernel.org,
james.smart@emulex.com, hch@infradead.org
Subject: Re: [Open-FCoE] [PATCH] fc: ensure scan_work isn't active when freeing fc_rport
Date: Tue, 10 Jun 2014 04:38:41 -0700 [thread overview]
Message-ID: <20140610113841.GC26195@infradead.org> (raw)
In-Reply-To: <20140609191637.GA3535@hmsreliant.think-freely.org>
On Mon, Jun 09, 2014 at 03:16:37PM -0400, Neil Horman wrote:
> > Given fcoe is quite mature now and its patches volume is very low, so
> > getting its kernel patches directly to scsi subsystem should work fine
> > and should be okay with James or Christophs to pull into scsi subsystem
> > directly once I've my non-author signoff ACK there as described in this
> > announcement at http://marc.info/?l=linux-scsi&m=140050839729415&w=2
> >
> > If no alternate suggestion or objection to this then I'll formally
> > announce this on fcoe mailing list.
> >
> > However for any huges patches series bomb or RFCs, I'll request fcoe
> > developers to send patches against scsi tree at fcoe devel list first
> > and then if needed I can roll them up.
> >
> > Thanks,
> > Vasu
> >
> Copy that Vasu, Christoph, is that ok with you?
That's fine with me. It would help greatly if you could make sure
all the paches get a review or two very quickly so I can just pick them
up immediately after reviewing them.
next prev parent reply other threads:[~2014-06-10 11:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-30 14:59 [PATCH] fc: ensure scan_work isn't active when freeing fc_rport Neil Horman
2014-06-02 8:35 ` Christoph Hellwig
2014-06-02 9:28 ` Hannes Reinecke
[not found] ` <1401461974-7879-1-git-send-email-nhorman-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>
2014-06-02 23:22 ` Vasu Dev
2014-06-06 20:54 ` Neil Horman
[not found] ` <20140606205409.GD2543-B26myB8xz7F8NnZeBjwnZQMhkBWG/bsMQH7oEaQurus@public.gmane.org>
2014-06-09 18:09 ` Vasu Dev
2014-06-09 19:16 ` [Open-FCoE] " Neil Horman
2014-06-10 11:38 ` Christoph Hellwig [this message]
[not found] ` <20140610113841.GC26195-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>
2014-06-10 15:49 ` Neil Horman
2014-06-16 11:15 ` [Open-FCoE] " Neil Horman
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=20140610113841.GC26195@infradead.org \
--to=hch@infradead.org \
--cc=fcoe-devel@open-fcoe.org \
--cc=james.smart@emulex.com \
--cc=linux-scsi@vger.kernel.org \
--cc=nhorman@tuxdriver.com \
--cc=vasu.dev@linux.intel.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 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).