From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH 5/5] shdmac: wire r8a7790
Date: Wed, 12 Feb 2014 21:23:07 +0000 [thread overview]
Message-ID: <52FBF448.3040207@cogentembedded.com> (raw)
In-Reply-To: <1392227964-7088-6-git-send-email-ben.dooks@codethink.co.uk>
On 02/12/2014 09:52 PM, Ben Dooks wrote:
>>> Add support for R8a7790 with new device tree code
>>> Note, does not yet moved the other of-dma user yet.
>> You didn't sign off.
> Sorry, this is still development, and didn't want people
> to apply it until it had an initial review.
In this case, it might have been worth marking them as RFC (request for
comments) in the subject. RFC patches are not applied.
[...]
>> WBR, Sergei
> Thanks.
Oh, not at all.
WBR, Sergei
prev parent reply other threads:[~2014-02-12 21:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-12 17:59 [PATCH 5/5] shdmac: wire r8a7790 Ben Dooks
2014-02-12 18:30 ` Sergei Shtylyov
2014-02-12 18:52 ` Ben Dooks
2014-02-12 21:23 ` Sergei Shtylyov [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=52FBF448.3040207@cogentembedded.com \
--to=sergei.shtylyov@cogentembedded.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 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).