netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
To: Giuseppe CAVALLARO <peppe.cavallaro@st.com>
Cc: Jon Mason <jon.mason@myri.com>, Joe Perches <joe@perches.com>,
	netdev <netdev@vger.kernel.org>,
	David Miller <davem@davemloft.net>,
	Paul Gortmaker <paul.gortmaker@windriver.com>,
	Jan Engelhardt <jengelh@medozas.de>,
	Andrew Gallatin <gallatin@myri.com>
Subject: Re: [RFC] Moving files around in drivers/net
Date: Thu, 23 Jun 2011 20:56:01 -0700	[thread overview]
Message-ID: <1308887762.995.10.camel@jtkirshe-mobl> (raw)
In-Reply-To: <4E033FE9.9060806@st.com>

[-- Attachment #1: Type: text/plain, Size: 979 bytes --]

On Thu, 2011-06-23 at 06:30 -0700, Giuseppe CAVALLARO wrote:
> On 6/16/2011 5:03 PM, Jon Mason wrote:
> >> stmmac may not be a good name.  Maybe stmicro.
> 
> Hello and sorry for the delay of this reply.
> 
> concerning the stmmac, in the past, I had thought to rename it as
> synmac
> because the driver, although was initially designed to work on ST
> platforms, today it runs on other platforms.
> The driver indeed is generic enough and is for MAC 10/100/1000 core by
> Synopsys.
> This is just an idea.
> 
> Moreover, sorry if I'm missing some details of this thread, I can do
> rework if you agree, so let me know how proceed.
> IIUC new patches should be built against:
> git://git.kernel.org/pub/scm/linux/kernel/git/jkirsher/next-organize
> 
> Regards
> Peppe 

I can make that change, I am almost finished re-working the patches with
the suggested changes so far, so I will try to get it into the next
update I post in the next couple of days.

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 490 bytes --]

  reply	other threads:[~2011-06-24  3:56 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-01 19:30 [RFC] Moving files around in drivers/net Joe Perches
2011-06-01 19:53 ` Jeff Kirsher
2011-06-01 20:01   ` Joe Perches
2011-06-15 18:38     ` Jeff Kirsher
2011-06-15 20:35       ` Andy Gospodarek
2011-06-16  1:10       ` Joe Perches
2011-06-16  3:34         ` Po-Yu Chuang
2011-06-20  1:42           ` Jeff Kirsher
2011-06-16  5:05         ` Sathya.Perla
2011-06-20  1:48           ` Jeff Kirsher
2011-06-16 14:14         ` Jon Mason
2011-06-20  1:51           ` Jeff Kirsher
2011-06-16 15:03         ` Jon Mason
2011-06-20  1:59           ` Jeff Kirsher
2011-06-20 15:23             ` Jon Mason
2011-06-23 13:30           ` Giuseppe CAVALLARO
2011-06-24  3:56             ` Jeff Kirsher [this message]
2011-06-20  2:25         ` Jeff Kirsher
2011-06-20  3:22           ` Ben Hutchings
2011-06-20  4:02             ` Jeff Kirsher
2011-06-20  5:23           ` Jan Engelhardt
2011-06-20  6:01             ` Joe Perches
2011-06-01 21:07 ` Ben Hutchings

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=1308887762.995.10.camel@jtkirshe-mobl \
    --to=jeffrey.t.kirsher@intel.com \
    --cc=davem@davemloft.net \
    --cc=gallatin@myri.com \
    --cc=jengelh@medozas.de \
    --cc=joe@perches.com \
    --cc=jon.mason@myri.com \
    --cc=netdev@vger.kernel.org \
    --cc=paul.gortmaker@windriver.com \
    --cc=peppe.cavallaro@st.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;
as well as URLs for NNTP newsgroup(s).