All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Tomoya MORINAGA" <tomoya-linux@dsn.okisemi.com>
To: "Marc Kleine-Budde" <mkl@pengutronix.de>
Cc: "Wolfgang Grandegger" <wg@grandegger.com>,
	"David S. Miller" <davem@davemloft.net>,
	"Wolfram Sang" <w.sang@pengutronix.de>,
	"Christian Pellegrin" <chripell@fsfe.org>,
	"Barry Song" <21cnbao@gmail.com>,
	"Samuel Ortiz" <sameo@linux.intel.com>,
	<socketcan-core@lists.berlios.de>, <netdev@vger.kernel.org>,
	"LKML" <linux-kernel@vger.kernel.org>,
	<andrew.chih.howe.khor@intel.com>, <qi.wang@intel.com>,
	<margie.foster@intel.com>, <yong.y.wang@intel.com>,
	"Masayuki Ohtake" <masa-korg@dsn.okisemi.com>,
	<kok.howg.ewe@intel.com>, <joel.clark@intel.com>
Subject: Re: [PATCH net-next-2.6 v2] can: Topcliff: PCH_CAN driver: Add Flow control,
Date: Tue, 16 Nov 2010 18:33:01 +0900	[thread overview]
Message-ID: <00a101cb8571$45165040$66f8800a@maildom.okisemi.com> (raw)
In-Reply-To: 4CE23D5A.5080606@pengutronix.de

Hi Marc,

On Tuesday, November 16, 2010 5:14 PM, Marc Kleine-Budde wrote :
> Sorry, but there is little chance to get a "this patch changes about 10
> things" into the kernel, please try to split up the patch.

Why !? I say again, it takes much time.
This doesn't make sense, does this?
Have I already updated almost your indications?

How about the following procedure?
I think the latest patch is pretty better than upstream's.
Thus,  firstly, could you accept the latest patch ?
After this, I will post patch per topic.

---
Thanks,

Tomoya MORINAGA
OKI SEMICONDUCTOR CO., LTD.


WARNING: multiple messages have this Message-ID (diff)
From: "Tomoya MORINAGA" <tomoya-linux-ECg8zkTtlr0C6LszWs/t0g@public.gmane.org>
To: "Marc Kleine-Budde" <mkl-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
Cc: andrew.chih.howe.khor-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org,
	Masayuki Ohtake
	<masa-korg-ECg8zkTtlr0C6LszWs/t0g@public.gmane.org>,
	Samuel Ortiz <sameo-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>,
	margie.foster-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org,
	netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	LKML <linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	socketcan-core-0fE9KPoRgkgATYTw5x5z8w@public.gmane.org,
	yong.y.wang-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org,
	kok.howg.ewe-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org,
	Wolfgang Grandegger <wg-5Yr1BZd7O62+XT7JhA+gdA@public.gmane.org>,
	joel.clark-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org,
	"David S. Miller" <davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>,
	Christian Pellegrin <chripell-VaTbYqLCNhc@public.gmane.org>,
	qi.wang-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org
Subject: Re: [PATCH net-next-2.6 v2] can: Topcliff: PCH_CAN driver: Add Flow control,
Date: Tue, 16 Nov 2010 18:33:01 +0900	[thread overview]
Message-ID: <00a101cb8571$45165040$66f8800a@maildom.okisemi.com> (raw)
In-Reply-To: 4CE23D5A.5080606@pengutronix.de

Hi Marc,

On Tuesday, November 16, 2010 5:14 PM, Marc Kleine-Budde wrote :
> Sorry, but there is little chance to get a "this patch changes about 10
> things" into the kernel, please try to split up the patch.

Why !? I say again, it takes much time.
This doesn't make sense, does this?
Have I already updated almost your indications?

How about the following procedure?
I think the latest patch is pretty better than upstream's.
Thus,  firstly, could you accept the latest patch ?
After this, I will post patch per topic.

---
Thanks,

Tomoya MORINAGA
OKI SEMICONDUCTOR CO., LTD.

  reply	other threads:[~2010-11-16  9:33 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-15  8:30 [PATCH net-next-2.6 v2] can: Topcliff: PCH_CAN driver: Add Flow control, Tomoya MORINAGA
2010-11-15  8:30 ` Tomoya MORINAGA
2010-11-15  9:11 ` Marc Kleine-Budde
2010-11-15  9:11   ` Marc Kleine-Budde
2010-11-16  5:18   ` Tomoya MORINAGA
2010-11-16  5:18     ` Tomoya MORINAGA
2010-11-16  8:14     ` Marc Kleine-Budde
2010-11-16  8:14       ` Marc Kleine-Budde
2010-11-16  9:33       ` Tomoya MORINAGA [this message]
2010-11-16  9:33         ` Tomoya MORINAGA
2010-11-16 17:11     ` David Miller
2010-11-16 17:11       ` David Miller
2010-11-15  9:37 ` Marc Kleine-Budde
2010-11-15  9:37   ` Marc Kleine-Budde
2010-11-16  5:30   ` Tomoya MORINAGA
2010-11-16  5:30     ` Tomoya MORINAGA
2010-11-15 14:21 ` Wolfgang Grandegger
2010-11-15 14:21   ` Wolfgang Grandegger
2010-11-16  8:25   ` Tomoya MORINAGA
2010-11-16  8:25     ` Tomoya MORINAGA
2010-11-16 10:16     ` Wolfgang Grandegger
2010-11-16 10:16       ` Wolfgang Grandegger
2010-11-19  7:36       ` Tomoya MORINAGA
2010-11-19  7:36         ` Tomoya MORINAGA
2010-11-19  8:57         ` Wolfgang Grandegger
2010-11-19  8:57           ` Wolfgang Grandegger
2010-11-22  5:20           ` Tomoya MORINAGA
2010-11-22  5:20             ` Tomoya MORINAGA

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='00a101cb8571$45165040$66f8800a@maildom.okisemi.com' \
    --to=tomoya-linux@dsn.okisemi.com \
    --cc=21cnbao@gmail.com \
    --cc=andrew.chih.howe.khor@intel.com \
    --cc=chripell@fsfe.org \
    --cc=davem@davemloft.net \
    --cc=joel.clark@intel.com \
    --cc=kok.howg.ewe@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=margie.foster@intel.com \
    --cc=masa-korg@dsn.okisemi.com \
    --cc=mkl@pengutronix.de \
    --cc=netdev@vger.kernel.org \
    --cc=qi.wang@intel.com \
    --cc=sameo@linux.intel.com \
    --cc=socketcan-core@lists.berlios.de \
    --cc=w.sang@pengutronix.de \
    --cc=wg@grandegger.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.