From: カオ ミン ヒェップ <cm-hiep@jinso.co.jp>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Mark Brown <broonie@kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
Linux-sh list <linux-sh@vger.kernel.org>,
Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>,
Geert Uytterhoeven <geert+renesas@linux-m68k.org>
Subject: Re: [RFC] spi: Using Trigger number to transmit/receive data
Date: Mon, 17 Mar 2014 12:01:40 +0000 [thread overview]
Message-ID: <5326E424.9040709@jinso.co.jp> (raw)
In-Reply-To: <CAMuHMdWP-tNCtnwP6=XZ1BNacWretVYjrpbT3R+KTEO=047+Nw@mail.gmail.com>
Hi Geert
On 03/17/2014 04:54 PM, Geert Uytterhoeven wrote:
> Hi Hiep,
>
> On Mon, Mar 17, 2014 at 2:11 AM, カオ ミン ヒェップ <cm-hiep@jinso.co.jp> wrote:
>> On 03/13/2014 06:23 PM, Geert Uytterhoeven wrote:
>>> On Thu, Mar 13, 2014 at 9:29 AM, Cao Minh Hiep <cm-hiep@jinso.co.jp>
>>> wrote:
>>>> In order to transmit and receive data when have 32 bytes of data that
>>>> ready has prepared on Transmit/Receive Buffer to transmit or receive.
>>>> Instead transmits/receives a byte data using Transmit/Receive Buffer
>>>> Data Triggering Number will improve the speed of transfer data.
>>> Thanks for your patch, this looks like a valuable improvement!
>>>
>>> Unfortunately your patch doesn't apply against spi/for-next anymore, as
>>> the driver has changed a lot lately, due to the addition of RZ/A1H and
>>> Quad/Dual support.
>>>
>> Thanks, Do you mean this patch did not need for next and I don't mind about
>> it?
> It means you will have to rework your patch to apply on top of
> https://git.kernel.org/cgit/linux/kernel/git/broonie/spi.git/tree/drivers/spi?h=for-next
> before the SPI maintainer can accept it.
Thanks, I understood, I will rework my patch and report to your later.
Cao Minh Hiep.
WARNING: multiple messages have this Message-ID (diff)
From: カオ ミン ヒェップ <cm-hiep@jinso.co.jp>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Mark Brown <broonie@kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
Linux-sh list <linux-sh@vger.kernel.org>,
Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>,
Geert Uytterhoeven <geert+renesas@linux-m68k.org>
Subject: Re: [RFC] spi: Using Trigger number to transmit/receive data
Date: Mon, 17 Mar 2014 21:01:40 +0900 [thread overview]
Message-ID: <5326E424.9040709@jinso.co.jp> (raw)
In-Reply-To: <CAMuHMdWP-tNCtnwP6=XZ1BNacWretVYjrpbT3R+KTEO=047+Nw@mail.gmail.com>
Hi Geert
On 03/17/2014 04:54 PM, Geert Uytterhoeven wrote:
> Hi Hiep,
>
> On Mon, Mar 17, 2014 at 2:11 AM, カオ ミン ヒェップ <cm-hiep@jinso.co.jp> wrote:
>> On 03/13/2014 06:23 PM, Geert Uytterhoeven wrote:
>>> On Thu, Mar 13, 2014 at 9:29 AM, Cao Minh Hiep <cm-hiep@jinso.co.jp>
>>> wrote:
>>>> In order to transmit and receive data when have 32 bytes of data that
>>>> ready has prepared on Transmit/Receive Buffer to transmit or receive.
>>>> Instead transmits/receives a byte data using Transmit/Receive Buffer
>>>> Data Triggering Number will improve the speed of transfer data.
>>> Thanks for your patch, this looks like a valuable improvement!
>>>
>>> Unfortunately your patch doesn't apply against spi/for-next anymore, as
>>> the driver has changed a lot lately, due to the addition of RZ/A1H and
>>> Quad/Dual support.
>>>
>> Thanks, Do you mean this patch did not need for next and I don't mind about
>> it?
> It means you will have to rework your patch to apply on top of
> https://git.kernel.org/cgit/linux/kernel/git/broonie/spi.git/tree/drivers/spi?h=for-next
> before the SPI maintainer can accept it.
Thanks, I understood, I will rework my patch and report to your later.
Cao Minh Hiep.
next prev parent reply other threads:[~2014-03-17 12:01 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-13 8:29 [RFC] spi: Using Trigger number to transmit/receive data Cao Minh Hiep
2014-03-13 8:29 ` Cao Minh Hiep
2014-03-13 8:29 ` Cao Minh Hiep
2014-03-13 8:29 ` Cao Minh Hiep
2014-03-13 9:23 ` Geert Uytterhoeven
2014-03-13 9:23 ` Geert Uytterhoeven
2014-03-17 1:11 ` カオ ミン ヒェップ
2014-03-17 1:11 ` カオ ミン ヒェップ
2014-03-17 7:54 ` Geert Uytterhoeven
2014-03-17 7:54 ` Geert Uytterhoeven
2014-03-17 12:01 ` カオ ミン ヒェップ [this message]
2014-03-17 12:01 ` カオ ミン ヒェップ
2014-03-17 19:48 ` Geert Uytterhoeven
2014-03-17 19:48 ` Geert Uytterhoeven
2014-03-17 20:32 ` Mark Brown
2014-03-19 0:50 ` カオ ミン ヒェップ
2014-03-19 0:50 ` カオ ミン ヒェップ
2014-03-19 1:17 ` Kuninori Morimoto
2014-03-19 1:17 ` Kuninori Morimoto
2014-03-13 9:27 ` Kuninori Morimoto
2014-03-13 9:27 ` Kuninori Morimoto
2014-03-17 1:15 ` カオ ミン ヒェップ
2014-03-17 1:15 ` カオ ミン ヒェップ
2014-03-13 14:17 ` Mark Brown
2014-03-17 1:16 ` カオ ミン ヒェップ
2014-03-17 1:16 ` カオ ミン ヒェップ
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=5326E424.9040709@jinso.co.jp \
--to=cm-hiep@jinso.co.jp \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=geert+renesas@linux-m68k.org \
--cc=geert@linux-m68k.org \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=linux-sh@vger.kernel.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 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.