From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Sarah Sharp <sarah.a.sharp@linux.intel.com>
Cc: linux-scsi <linux-scsi@vger.kernel.org>,
Alan Stern <stern@rowland.harvard.edu>,
USB list <linux-usb@vger.kernel.org>
Subject: Re: [PATCH 0/2] target refcounting infrastructure fixes for usb
Date: Fri, 07 Mar 2014 13:21:02 +0400 [thread overview]
Message-ID: <1394184062.5225.30.camel@dabdike> (raw)
In-Reply-To: <20140306231827.GA5307@xanatos>
On Thu, 2014-03-06 at 15:18 -0800, Sarah Sharp wrote:
> Hi James,
>
> Sorry for the extremely late ack.
That's OK ... my original plan was to send them in the last merge window
even without your ack, but that got a bit derailed, so I'll do it in
this one with.
> These patches work fine when applied
> against 3.14-rc5, and I can't trigger the oops anymore. Hans' UAS
> patches are going to be queued for 3.15. Any chance of these patches
> making it into 3.15 as well?
Yes, the plan is to queue for 3.15 and request a delayed backport to
stable in case any of the extensive logic changes triggers another bug
in the field.
James
next prev parent reply other threads:[~2014-03-07 9:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-21 14:58 [PATCH 0/2] target refcounting infrastructure fixes for usb James Bottomley
[not found] ` <1390316319.2182.9.camel-sFMDBYUN5F8GjUHQrlYNx2Wm91YjaHnnhRte9Li2A+AAvxtiuMwx3w@public.gmane.org>
2014-01-21 15:00 ` [PATCH 1/2] fix our current target reap infrastructure James Bottomley
2014-03-06 23:18 ` [PATCH 0/2] target refcounting infrastructure fixes for usb Sarah Sharp
2014-03-07 9:21 ` James Bottomley [this message]
2014-01-21 15:01 ` [PATCH 2/2] dual scan thread bug fix James Bottomley
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=1394184062.5225.30.camel@dabdike \
--to=james.bottomley@hansenpartnership.com \
--cc=linux-scsi@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=sarah.a.sharp@linux.intel.com \
--cc=stern@rowland.harvard.edu \
/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