From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: 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 14:58:51 +0800 [thread overview]
Message-ID: <20130305065851.GA30028@kroah.com> (raw)
In-Reply-To: <1362464958-8722-1-git-send-email-ganesanr@broadcom.com>
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?
> --- /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?
> --- /dev/null
> +++ b/drivers/staging/netlogic/TODO
> @@ -0,0 +1,5 @@
> +* Implementing 64bit stat counter in software
> +* All memory allocation should be changed to DMA allocations
> +* All the netdev should be linked to single pdev as parent
> +* Changing comments in to linux standred format
> +
I need a name and email address for who is responsible for this driver
and will be handling patches for it.
Please fix this up and resubmit.
thanks,
greg k-h
next prev parent reply other threads:[~2013-03-05 6:58 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 [this message]
2013-03-05 14:13 ` Ganesan Ramalignam
2013-03-05 14:19 ` Greg Kroah-Hartman
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=20130305065851.GA30028@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