From: Wolfram Sang <wsa@the-dreams.de>
To: linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH V2 1/5] ARM: shmobile: r8a7791: add IIC0/1 clock macros
Date: Wed, 26 Mar 2014 06:29:33 +0000 [thread overview]
Message-ID: <20140326062933.GA2664@katana> (raw)
In-Reply-To: <CANqRtoSYTSZV-wxXBeGWYnPLPGZNL3WEtXgHh1U8CQxAEhx5zQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 555 bytes --]
> To clarify, I can't seem to find any cover letter for this series, so
> instead I will with this email reply to [1/1]. Here is also a list of
> the patches that I believe are part of this series, please correct me
> if I'm wrong:
You are absolutely right.
> They all look good to me!
>
> Acked-by: Magnus Damm <damm@opensource.se>
Thanks!
> Simon, can you please pick up these changes? I believe there are no
> special dependencies.
The dependencies (pfc entries and new compatible for the driver) are
already in linux-next.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2014-03-26 6:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-10 11:26 [PATCH V2 1/5] ARM: shmobile: r8a7791: add IIC0/1 clock macros Wolfram Sang
2014-03-10 11:26 ` [PATCH V2 2/5] ARM: shmobile: r8a7791: add IIC(B) clocks to dtsi Wolfram Sang
2014-03-10 11:26 ` [PATCH V2 3/5] ARM: shmobile: r8a7791: add IIC(B) cores " Wolfram Sang
2014-08-21 20:53 ` Sergei Shtylyov
2014-03-10 11:26 ` [PATCH V2 4/5] ARM: shmobile: koelsch: make i2c2-pfc node unique Wolfram Sang
2014-03-10 11:27 ` [PATCH V2 5/5] ARM: shmobile: koelsch: activate i2c6 bus Wolfram Sang
2014-03-10 11:36 ` [PATCH V2 1/5] ARM: shmobile: r8a7791: add IIC0/1 clock macros Laurent Pinchart
2014-03-26 5:09 ` Magnus Damm
2014-03-26 6:29 ` Wolfram Sang [this message]
2014-03-26 17:15 ` Simon Horman
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=20140326062933.GA2664@katana \
--to=wsa@the-dreams.de \
--cc=linux-arm-kernel@lists.infradead.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).