All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Masayuki Ohtake" <masa-korg@dsn.okisemi.com>
To: "Eric Dumazet" <eric.dumazet@gmail.com>
Cc: "David S. Miller" <davem@davemloft.net>,
	"Randy Dunlap" <randy.dunlap@oracle.com>,
	"John Linn" <john.linn@xilinx.com>,
	"Ralf Baechle" <ralf@linux-mips.org>,
	"Kristoffer Glembo" <kristoffer@gaisler.com>,
	"Maxime Bizon" <mbizon@freebox.fr>,
	"Greg Rose" <gregory.v.rose@intel.com>,
	"ML netdev" <netdev@vger.kernel.org>,
	"LKML" <linux-kernel@vger.kernel.org>,
	"Toshiharu Okada" <okada533@dsn.okisemi.com>,
	"Takahiro Shimizu" <shimizu394@dsn.okisemi.com>,
	"Tomoya Morinaga" <morinaga526@dsn.okisemi.com>,
	"Wang, Qi" <qi.wang@intel.com>,
	"Wang, Yong Y" <yong.y.wang@intel.com>,
	"Andrew" <andrew.chih.howe.khor@intel.com>,
	"Intel OTC" <joel.clark@intel.com>,
	"Foster, Margie" <margie.foster@intel.com>,
	"MeeGo" <meego-dev@meego.com>
Subject: Re: [PATCH v6] Gigabit Ethernet driver of Topcliff PCH
Date: Mon, 27 Sep 2010 15:39:57 +0900	[thread overview]
Message-ID: <002c01cb5e0e$d23087a0$66f8800a@maildom.okisemi.com> (raw)
In-Reply-To: 1285567800.2357.565.camel@edumazet-laptop

Hi Eric

Thank you for information.
I did not know "net-next-2.6."
This driver is not changed.

Thanks, Ohtake
-----
Date: Mon, 27 Sep 2010 08:10:00 +0200
From: "Eric Dumazet" <eric.dumazet@gmail.com>


> Le lundi 27 septembre 2010 a 14:54 +0900, Masayuki Ohtake a ecrit :
> > Gigabit Ethernet driver of Topcliff PCH
> >
> > Topcliff PCH is the platform controller hub that is going to be used in
> > Intel's upcoming general embedded platform. All IO peripherals in
> > Topcliff PCH are actually devices sitting on AMBA bus.
> > Topcliff PCH has Gigabit Ethernet I/F. Using this I/F, it is able to
> > access system devices connected to Gigabit Ethernet.
> >
> > Signed-off-by: Masayuki Ohtake <masa-korg@dsn.okisemi.com>
> > ---
>
> Hmm, what is going on ?
>
> David already put your driver in net-next-2.6
>
> http://git.kernel.org/?p=linux/kernel/git/davem/net-next-2.6.git;a=commit;h=77555ee7228234257957fd54daa0b69178906320
>
> If you want to make changes, you have to send diffs now, not the full
> version.





  reply	other threads:[~2010-09-27  6:40 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-27  5:54 [PATCH v6] Gigabit Ethernet driver of Topcliff PCH Masayuki Ohtake
2010-09-27  5:54 ` Masayuki Ohtake
2010-09-27  6:10 ` Eric Dumazet
2010-09-27  6:39   ` Masayuki Ohtake [this message]
2010-09-27  6:47     ` David Miller
2010-09-27  7:18       ` Masayuki Ohtake
2010-09-27  6:44 ` David Miller
     [not found] ` <AANLkTinedgQJq04PHdGmZqs4p6Du4PA16QC2JNTaGhAa@mail.gmail.com>
2010-10-19  5:30   ` Masayuki Ohtake

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='002c01cb5e0e$d23087a0$66f8800a@maildom.okisemi.com' \
    --to=masa-korg@dsn.okisemi.com \
    --cc=andrew.chih.howe.khor@intel.com \
    --cc=davem@davemloft.net \
    --cc=eric.dumazet@gmail.com \
    --cc=gregory.v.rose@intel.com \
    --cc=joel.clark@intel.com \
    --cc=john.linn@xilinx.com \
    --cc=kristoffer@gaisler.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=margie.foster@intel.com \
    --cc=mbizon@freebox.fr \
    --cc=meego-dev@meego.com \
    --cc=morinaga526@dsn.okisemi.com \
    --cc=netdev@vger.kernel.org \
    --cc=okada533@dsn.okisemi.com \
    --cc=qi.wang@intel.com \
    --cc=ralf@linux-mips.org \
    --cc=randy.dunlap@oracle.com \
    --cc=shimizu394@dsn.okisemi.com \
    --cc=yong.y.wang@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.