From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Ganesan Ramalignam <ganesanr@broadcom.com>
Cc: Ralf Baechle <ralf@linux-mips.org>, linux-mips@linux-mips.org
Subject: Re: [PATCH] Staging: Netlogic XLR/XLS GMAC driver
Date: Tue, 5 Mar 2013 22:19:29 +0800 [thread overview]
Message-ID: <20130305141929.GA4434@kroah.com> (raw)
In-Reply-To: <20130305141353.GB29102@ganesanr.netlogicmircro.com>
On Tue, Mar 05, 2013 at 07:43:54PM +0530, Ganesan Ramalignam wrote:
> On Tue, Mar 05, 2013 at 02:58:51PM +0800, Greg Kroah-Hartman wrote:
> > On Tue, Mar 05, 2013 at 11:59:18AM +0530, ganesanr@broadcom.com wrote:
> > > This patch has to be merged via staging tree.
> > >
> > > This driver has been submitted to netdev tree and reviewed, the comments
> > > are list in TODO list, will be addressed in next cycle of submission, till
> > > that time I wanted this driver to be in staging tree.
> > >
> > > This driver shall be sent to netdev@vger.kernel.org and David Miller <davem@davemloft.net>
> > > for further review.
> >
> > When is that going to happen?
> >
>
> In two months.
Why then? What is so magic about 2 months? In two months, this driver
is not going to be in a released version of the kernel yet.
> > > --- /dev/null
> > > +++ b/drivers/staging/netlogic/Kconfig
> > > @@ -0,0 +1,7 @@
> > > +config NETLOGIC_XLR_NET
> > > + tristate "Netlogic XLR/XLS network device"
> > > + depends on CPU_XLR
> >
> > Why will this not build on any other platform? It should, right?
> >
> >
>
> This driver is for XLR processor ethernet, which is depend on FMN
> for any communication between packet processing agents, so this driver
> depend on XLR platform.
What is "FMN"?
thanks,
greg k-h
next prev parent reply other threads:[~2013-03-05 14:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-05 6:29 [PATCH] Staging: Netlogic XLR/XLS GMAC driver ganesanr
2013-03-05 6:58 ` Greg Kroah-Hartman
2013-03-05 14:13 ` Ganesan Ramalignam
2013-03-05 14:19 ` Greg Kroah-Hartman [this message]
2013-03-05 16:14 ` Ganesan Ramalignam
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=20130305141929.GA4434@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=ganesanr@broadcom.com \
--cc=linux-mips@linux-mips.org \
--cc=ralf@linux-mips.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