From: "Tomoya MORINAGA" <tomoya-linux@dsn.okisemi.com>
To: "'Greg KH'" <greg@kroah.com>
Cc: "'Greg Kroah-Hartman'" <gregkh@suse.de>,
"'Alan Cox'" <alan@linux.intel.com>,
<linux-kernel@vger.kernel.org>, <qi.wang@intel.com>,
<yong.y.wang@intel.com>, <joel.clark@intel.com>,
<kok.howg.ewe@intel.com>, <toshiharu-linux@dsn.okisemi.com>
Subject: RE: [PATCH 1/8] pch_uart: add multi-scatter processing
Date: Wed, 23 Feb 2011 09:13:15 +0900 [thread overview]
Message-ID: <0180FEFC7EED4640A1AF46ECCFA60FF1@hacdom.okisemi.com> (raw)
In-Reply-To: <20110222235133.GA31831@kroah.com>
Hi Greg,
On Wednesday, February 23, 2011 8:52 AM, Greg KH wrote:
> What kernel tree did you make this against? the pch_uart.c
> file is not in this location anymore.
>
> Care to redo this series against the linux-next tree so that
> I can apply it properly?
this patch series is for linux-next.
I will repost the patches again.
[PATCH 1/8] -> [PATCH linux-next 1/8]
Thanks,
-----------------------------------------
Tomoya MORINAGA
OKI SEMICONDUCTOR CO., LTD.
prev parent reply other threads:[~2011-02-23 0:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-18 2:23 Tomoya MORINAGA
2011-02-18 2:23 ` [PATCH 2/8] pch_uart: add spin_lock_init Tomoya MORINAGA
2011-02-18 2:23 ` [PATCH 3/8] pch_uart : Reduce memcpy Tomoya MORINAGA
2011-02-18 2:24 ` [PATCH 4/8] pch_uart : Use dev_xxx not pr_xxx Tomoya MORINAGA
2011-02-18 2:24 ` [PATCH 5/8] pch_uart: fix uart clock setting issue Tomoya MORINAGA
2011-02-18 2:24 ` [PATCH 6/8] pch_uart: fix auto flow control miss-setting issue Tomoya MORINAGA
2011-02-18 2:24 ` [PATCH 7/8] pch_uart: fix exclusive access issue Tomoya MORINAGA
2011-02-18 2:24 ` [PATCH 8/8] pch_uart: Fix DMA channel miss-setting issue Tomoya MORINAGA
2011-02-22 23:51 ` [PATCH 1/8] pch_uart: add multi-scatter processing Greg KH
2011-02-23 0:13 ` Tomoya MORINAGA [this message]
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=0180FEFC7EED4640A1AF46ECCFA60FF1@hacdom.okisemi.com \
--to=tomoya-linux@dsn.okisemi.com \
--cc=alan@linux.intel.com \
--cc=greg@kroah.com \
--cc=gregkh@suse.de \
--cc=joel.clark@intel.com \
--cc=kok.howg.ewe@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=qi.wang@intel.com \
--cc=toshiharu-linux@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®