From: Greg KH <greg@kroah.com>
To: J Freyensee <james_p_freyensee@linux.intel.com>
Cc: gregkh@suse.de, linux-kernel@vger.kernel.org,
suhail.ahmed@intel.com, christophe.guerard@intel.com
Subject: Re: [PATCH 10/10] n_tracerouter and n_tracesink compile configurations.
Date: Fri, 25 Feb 2011 10:45:38 -0800 [thread overview]
Message-ID: <20110225184538.GA2372@kroah.com> (raw)
In-Reply-To: <1298659152.3156.8.camel@localhost>
On Fri, Feb 25, 2011 at 10:39:12AM -0800, J Freyensee wrote:
> On Fri, 2011-02-25 at 10:00 -0800, Greg KH wrote:
> > On Thu, Feb 24, 2011 at 10:07:04AM -0800, james_p_freyensee@linux.intel.com wrote:
> > > From: J Freyensee <james_p_freyensee@linux.intel.com>
> > >
> > > This patch allows n_tracerouter and n_tracesink to be compiled and
> > > configured in the Linux kernel.
> > >
> > > Signed-off-by: J Freyensee <james_p_freyensee@linux.intel.com>
> > > ---
> > > drivers/char/Kconfig | 32 ++++++++++++++++++++++++++++++++
> >
> > Why drivers/char/Kconfig? This should be in drivers/tty/Kconfig, right?
> >
> > Yes, this is a recent change, see the linux-next tree for the addition
> > of this file :)
> >
>
> That is what I was going to ask because I did base this patch off of the
> 2.6.37 stable tree and did not see a drivers/tty/Kconfig :-O. I figured
> the stable branch was the better choice since you own it and I need to
> go through you for my work.
You should always submit against linux-next as that's pretty close to
the tree that we would be able to apply your patches to. We can't go
back in time and add them to 2.6.37 :)
> So I should pull from linux-next I guess to fix the changes mentioned
> this round?:
>
> -Thomas's comments on Patch 9.
> -These issues in this patch
Yes.
thanks,
greg k-h
next prev parent reply other threads:[~2011-02-25 18:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-24 18:07 [PATCH 10/10] n_tracerouter and n_tracesink compile configurations james_p_freyensee
2011-02-25 18:00 ` Greg KH
2011-02-25 18:39 ` J Freyensee
2011-02-25 18:45 ` Greg KH [this message]
2011-02-25 18:01 ` 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=20110225184538.GA2372@kroah.com \
--to=greg@kroah.com \
--cc=christophe.guerard@intel.com \
--cc=gregkh@suse.de \
--cc=james_p_freyensee@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=suhail.ahmed@intel.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