From: Greg KH <greg@kroah.com>
To: Wu Fengguang <fengguang.wu@intel.com>
Cc: Greg KH <gregkh@suse.de>, Marcel Holtmann <marcel@holtmann.org>,
LKML <linux-kernel@vger.kernel.org>,
Jason Baron <jbaron@redhat.com>
Subject: Re: [PATCH] dynamic_printk: add line feed to printk
Date: Fri, 12 Dec 2008 11:08:15 -0800 [thread overview]
Message-ID: <20081212190815.GC2950@kroah.com> (raw)
In-Reply-To: <20081210234317.GA5904@localhost>
On Thu, Dec 11, 2008 at 07:43:17AM +0800, Wu Fengguang wrote:
> On Wed, Dec 10, 2008 at 05:23:23PM +0200, Greg Kroah-Hartman wrote:
> > On Wed, Dec 10, 2008 at 10:40:58PM +0800, Wu Fengguang wrote:
> > > On Wed, Dec 10, 2008 at 12:18:46PM +0200, Marcel Holtmann wrote:
> > > > Hi,
> > > >
> > > > > Append '\n' to two printk messages.
> > > >
> > > > I already sent a patch for that and Greg picked it up.
> > >
> > > No I didn't find it in the usb-2.6 tree:
> > >
> > > git pull git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb-2.6.git
> > > >From git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb-2.6
> > > * branch HEAD -> FETCH_HEAD
> > > Already up-to-date.
> >
> > That's not the "usb" tree, if you read the description, it should be
> > clear.
>
> Yup, it reads "junk tree, please ignore". When I first found it in
> git.kernel.org, I chose to trust the name 'usb-2.6' instead of its
> description...
Heh, as if I just added that description for the fun of it :)
> > My tree is in quilt, please see the MAINTAINERS file for details.
>
> Got it. Below is the updated patch based on Marcel's one.
Thanks, I'll queue it up.
grg k-h
prev parent reply other threads:[~2008-12-12 19:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-10 7:33 [PATCH] dynamic_printk: add line feed to printk Wu Fengguang
2008-12-10 10:18 ` Marcel Holtmann
2008-12-10 14:40 ` Wu Fengguang
2008-12-10 15:01 ` Marcel Holtmann
2008-12-10 15:23 ` Greg KH
2008-12-10 23:43 ` Wu Fengguang
2008-12-11 15:25 ` Jason Baron
2008-12-12 19:08 ` 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=20081212190815.GC2950@kroah.com \
--to=greg@kroah.com \
--cc=fengguang.wu@intel.com \
--cc=gregkh@suse.de \
--cc=jbaron@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marcel@holtmann.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.