From: Greg KH <greg@kroah.com>
To: Jason Wessel <jason.wessel@windriver.com>
Cc: linux-kernel@vger.kernel.org,
kgdb-bugreport@lists.sourceforge.net, mingo@elte.hu,
Greg Kroah-Hartman <gregkh@suse.de>,
Eric Biederman <ebiederm@xmission.com>,
Yinghai Lu <yhlu.kernel@gmail.com>,
linux-usb@vger.kernel.org
Subject: Re: [PATCH 7/8] ehci-dbgp: split PID register updates for IN and OUT pipes
Date: Thu, 18 Feb 2010 14:22:15 -0800 [thread overview]
Message-ID: <20100218222215.GA27855@kroah.com> (raw)
In-Reply-To: <4B7DB912.70806@windriver.com>
On Thu, Feb 18, 2010 at 04:02:58PM -0600, Jason Wessel wrote:
> Greg KH wrote:
> > On Fri, Feb 12, 2010 at 04:39:28PM -0600, Jason Wessel wrote:
> >
> >> This patch addresses two problems:
> >>
> >
> > Do you want me to take this patch, and 8/8 in my tree, or yours?
> >
> > If yours, please add a:
> > Acked-by: Greg Kroah-Hartman <gregkh@suse.de>
> > to the patch.
> >
> >
>
>
> I added the Ack's.
>
> I will keep the patches in my tree because unless the
> kernel-parameters.txt patch is split it will not apply cleanly for patch
> 8/8. It currently depends on the kdb tree, even though the source code
> portions do not depend on anything. If the early debug patch set is
> rejected for some reason, I'll fix patch 8/8 and submit it to your tree.
Sounds good.
> You might consider patch 7/8 for -stable because I observed the dbgp
> device no longer dropping any characters when there is a significant
> printk volume in a short period of time.
When the patch goes into Linus's tree, just send stable@kernel.org the
git commit id of the patch and I will add it.
Or you can add:
Cc: stable <stable@kernel.org>
to the signed-off-by area, and when it goes into Linus's tree, I will be
automatically notified about it, no need for you to do anything else.
thanks,
greg k-h
next prev parent reply other threads:[~2010-02-18 22:23 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-12 22:39 [PATCH 0/7] early debugging kgdb & kdb proposed merge for 2.6.34 Jason Wessel
2010-02-12 22:39 ` [PATCH 1/8] x86, kgdb: early trap init for early debug Jason Wessel
2010-02-12 22:39 ` [PATCH 2/8] x86, kgdb, init: Add early and late debug states Jason Wessel
2010-02-12 22:39 ` [PATCH 3/8] x86,kgdb: Implement early hardware breakpoint debugging Jason Wessel
2010-02-12 22:39 ` [PATCH 4/8] x86,early dr regs,kgdb: Allow kernel debugger early dr register access Jason Wessel
2010-02-12 22:39 ` [PATCH 5/8] kgdboc: Add ekgdboc for early use of the kernel debugger Jason Wessel
2010-02-12 22:39 ` [PATCH 6/8] earlyprintk,vga,kdb: Fix \b and \r for earlyprintk=vga with kdb Jason Wessel
2010-02-12 22:39 ` [PATCH 7/8] ehci-dbgp: split PID register updates for IN and OUT pipes Jason Wessel
2010-02-18 0:01 ` Greg KH
2010-02-18 22:02 ` Jason Wessel
2010-02-18 22:22 ` Greg KH [this message]
2010-02-12 22:39 ` [PATCH 8/8] echi-dbgp: Add kernel debugger support for the usb debug port Jason Wessel
-- strict thread matches above, loose matches on Subject: below --
2010-02-25 21:21 [GIT PULL] kdb / early debug (2 of 2) Jason Wessel
2010-02-25 21:22 ` [PATCH 7/8] ehci-dbgp: split PID register updates for IN and OUT pipes Jason Wessel
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=20100218222215.GA27855@kroah.com \
--to=greg@kroah.com \
--cc=ebiederm@xmission.com \
--cc=gregkh@suse.de \
--cc=jason.wessel@windriver.com \
--cc=kgdb-bugreport@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=yhlu.kernel@gmail.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 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.