From: Felipe Balbi <balbi@kernel.org>
To: Yoshihiro Shimoda <yoshihiro.shimoda.uh@renesas.com>
Cc: "gregkh\@linuxfoundation.org" <gregkh@linuxfoundation.org>,
"linux-usb\@vger.kernel.org" <linux-usb@vger.kernel.org>,
"linux-renesas-soc\@vger.kernel.org"
<linux-renesas-soc@vger.kernel.org>,
"stable\@vger.kernel.org" <stable@vger.kernel.org>
Subject: RE: [PATCH v2 0/2] usb: renesas_usbhs: fix to avoid unexpected condition
Date: Tue, 22 Mar 2016 09:15:55 +0200 [thread overview]
Message-ID: <87zitrx9sk.fsf@intel.com> (raw)
In-Reply-To: <TY1PR06MB09286508DBFE88441FA6038ED8800@TY1PR06MB0928.apcprd06.prod.outlook.com>
[-- Attachment #1: Type: text/plain, Size: 587 bytes --]
Yoshihiro-san,
Yoshihiro Shimoda <yoshihiro.shimoda.uh@renesas.com> writes:
>> From: Yoshihiro Shimoda
>> Sent: Thursday, March 10, 2016 11:30 AM
>>
>> This patch set is based on the latest Felipe's usb.git / testing/next branch.
>> (commit id = ac5706631325ae3695bfa1527101ab2b2f64859f)
>
> Would you review the patch set?
>
> I confirmed that the patch set could be applied on the latest
> testing/next and testing/fixes branches.
I'm waiting for v4.6-rc1 to be tagged to carry on applying
patches. Nothing really happens during the merge window ;-)
--
balbi
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 818 bytes --]
next prev parent reply other threads:[~2016-03-22 7:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-10 2:30 [PATCH v2 0/2] usb: renesas_usbhs: fix to avoid unexpected condition Yoshihiro Shimoda
2016-03-10 2:30 ` [PATCH v2 1/2] usb: renesas_usbhs: avoid NULL pointer derefernce in usbhsf_pkt_handler() Yoshihiro Shimoda
2016-03-10 2:30 ` [PATCH v2 2/2] usb: renesas_usbhs: disable TX IRQ before starting TX DMAC transfer Yoshihiro Shimoda
2016-03-22 6:50 ` [PATCH v2 0/2] usb: renesas_usbhs: fix to avoid unexpected condition Yoshihiro Shimoda
2016-03-22 7:15 ` Felipe Balbi [this message]
2016-03-22 7:21 ` Yoshihiro Shimoda
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=87zitrx9sk.fsf@intel.com \
--to=balbi@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=yoshihiro.shimoda.uh@renesas.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