From: Sergei Shtylyov <sshtylyov@mvista.com>
To: Greg KH <gregkh@suse.de>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org
Subject: Re: [GIT PATCH] USB patches for 3.1
Date: Tue, 26 Jul 2011 15:03:42 +0400 [thread overview]
Message-ID: <4E2E9F0E.4060703@ru.mvista.com> (raw)
In-Reply-To: <20110726045903.GA2354@kroah.com>
Hello.
On 26-07-2011 8:59, Greg KH wrote:
> Here's the big USB pull request for your 3.1 tree.
> Note, there will be one conflict in the
> Documentation/feature-removal-schedule.txt file, when you merge this,
> but it's trivial to resolve.
> Please pull from:
> master.kernel.org:/pub/scm/linux/kernel/git/gregkh/usb-2.6.git/ usb-next
> All of these patches have been in the linux-next and mm trees for a
> number of weeks.
> The full patches will be sent to the linux-usb mailing list, if anyone
> wants to see them.
Looks like those patches didn't reach the list...
> thanks,
> greg k-h
WBR, Sergei
next prev parent reply other threads:[~2011-07-26 11:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-26 4:59 [GIT PATCH] USB patches for 3.1 Greg KH
2011-07-26 11:03 ` Sergei Shtylyov [this message]
2011-07-27 4:14 ` Greg KH
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=4E2E9F0E.4060703@ru.mvista.com \
--to=sshtylyov@mvista.com \
--cc=akpm@linux-foundation.org \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=torvalds@linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox