From: Greg KH <greg@kroah.com>
To: Jack Pham <jackp@codeaurora.org>
Cc: Alan Stern <stern@rowland.harvard.edu>,
linux-usb@vger.kernel.org, Manu Gautam <mgautam@codeaurora.org>,
Tim Sander <tim@krieglstein.org>,
linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH 2/2] usb: ehci: Add support for SINGLE_STEP_SET_FEATURE test of EHSET
Date: Thu, 8 Aug 2013 19:32:23 -0700 [thread overview]
Message-ID: <20130809023223.GA4002@kroah.com> (raw)
In-Reply-To: <20130809021213.GB28634@usblab-sd-06.qualcomm.com>
On Thu, Aug 08, 2013 at 07:12:13PM -0700, Jack Pham wrote:
> Hi Greg,
>
> On Thu, Aug 08, 2013 at 05:05:41PM -0700, Greg KH wrote:
> > I don't seem to have a patch 1/2 from you, did it not get sent somehow?
>
> Here was patch 1/2: http://marc.info/?l=linux-usb&m=137282127113409&w=2
> which you've applied to usb-next already as commit 1353aa53. I kept the
> sequence numbering in the subject as it was in response to the RFC
> version I originally sent which was the 2/2. Should I resend this as a
> standalone (i.e. with a revised subject tag) instead?
Ah, ok. Given that this was about 500+ patches ago in my review queue,
I didn't remember it at all :)
In the future, when resending something like this, when the 1/2 patch is
already accepted, just send it as 1/1, as there is no patch it depends
on outstanding.
thanks,
greg k-h
prev parent reply other threads:[~2013-08-09 2:31 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1591113.JYQdTBbFW7@dabox>
2013-07-03 3:13 ` [PATCH 0/2] usb: Add support for EHSET Jack Pham
2013-07-03 3:13 ` [PATCH 1/2] usb: misc: EHSET Test Fixture device driver for host compliance Jack Pham
2013-07-03 3:13 ` [RFC/PATCH 2/2] usb: ehci: Add support for SINGLE_STEP_SET_FEATURE test of EHSET Jack Pham
2013-07-25 18:46 ` Greg KH
2013-07-25 19:44 ` Alan Stern
2013-07-25 20:54 ` Felipe Balbi
2013-07-25 21:33 ` Alan Stern
2013-08-09 13:41 ` Felipe Balbi
2013-08-09 14:37 ` Alan Stern
2013-08-09 14:44 ` Felipe Balbi
2013-08-09 15:04 ` Alan Stern
[not found] ` <Pine.LNX.4.44L0.1308091053450.1405-100000-IYeN2dnnYyZXsRXLowluHWD2FQJk+8+b@public.gmane.org>
2013-08-12 17:53 ` Felipe Balbi
2013-08-12 18:52 ` Alan Stern
2013-08-13 15:32 ` Felipe Balbi
2013-08-13 16:47 ` Alan Stern
2013-08-13 23:05 ` Jack Pham
2013-08-14 14:10 ` Alan Stern
2013-08-14 17:05 ` Jack Pham
2013-07-25 22:09 ` Jack Pham
[not found] ` <20130725220925.GA28634-NjF/qFWh7jSrUKQWM4GlyCPyLMyjRtWwAL8bYrjMMd8@public.gmane.org>
2013-08-08 23:49 ` [PATCH " Jack Pham
2013-08-09 0:05 ` Greg KH
2013-08-09 2:12 ` Jack Pham
2013-08-09 2:32 ` Greg KH [this message]
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=20130809023223.GA4002@kroah.com \
--to=greg@kroah.com \
--cc=jackp@codeaurora.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mgautam@codeaurora.org \
--cc=stern@rowland.harvard.edu \
--cc=tim@krieglstein.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 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.