public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Amit S. Kale" <amitkale@emsyssoft.com>
To: Tom Rini <trini@kernel.crashing.org>
Cc: kgdb-bugreport@lists.sourceforge.net,
	Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [Kgdb-bugreport] Move eth into 'lite' series?
Date: Tue, 23 Mar 2004 10:32:54 +0530	[thread overview]
Message-ID: <200403231032.55545.amitkale@emsyssoft.com> (raw)
In-Reply-To: <20040322144112.GA27175@smtp.west.cox.net>

On Monday 22 Mar 2004 8:11 pm, Tom Rini wrote:
> On Sat, Mar 20, 2004 at 12:42:21PM +0530, Amit S. Kale wrote:
> > On Saturday 20 Mar 2004 2:33 am, Tom Rini wrote:
> > > I was thinking, now that netpoll is in 2.6.5-rc1, should we move the
> > > kgdboe driver into the -lite series?  I'd like to say Yes, with a quick
> > > check over the include list.
> >
> > Let's wait till current session to push kgdb into mainline kernel is
> > over. We need not push kgdboe into lite series, we can push it into
> > mainline kernel itself :-)
> >
> > I was supposed to submit second version of lite patches monday this week,
> > but was preempted by some other work. I'll post them on coming monday now
>
> Actually, I was thinking just the opposite.  Based on Linus' comments
> (see http://www.ussg.iu.edu/hypermail/linux/kernel/0211.1/1861.html and
> maybe http://www.ussg.iu.edu/hypermail/linux/kernel/0211.2/0089.html
> too) we can always try and get the 8250 serial backend in once kgdb +
> enet driver is already in.

That's true. kgdboe wasn't quite ready last month, otherwise we could have 
gone that way. Let's now change our direction right now. Let's push whatever 
we have. If it doesn't go in, we'll switch to eth driver instead.

-Amit


      reply	other threads:[~2004-03-23  5:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-19 21:03 Move eth into 'lite' series? Tom Rini
2004-03-20  7:12 ` [Kgdb-bugreport] " Amit S. Kale
2004-03-22 14:41   ` Tom Rini
2004-03-23  5:02     ` Amit S. Kale [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=200403231032.55545.amitkale@emsyssoft.com \
    --to=amitkale@emsyssoft.com \
    --cc=kgdb-bugreport@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=trini@kernel.crashing.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