From: geert@linux-m68k.org (Geert Uytterhoeven)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 0/3] Add R8A7743/SK-RZG1M PFC support
Date: Wed, 7 Jun 2017 19:52:20 +0200 [thread overview]
Message-ID: <CAMuHMdUDO-+F_fOf4Z1ZPdZhs_MBn8J6ig-Pn4K0oMvv-EM2gw@mail.gmail.com> (raw)
In-Reply-To: <4937ae78-8800-1a11-547b-2269d063d45a@cogentembedded.com>
Hi Sergei,
On Wed, Jun 7, 2017 at 6:16 PM, Sergei Shtylyov
<sergei.shtylyov@cogentembedded.com> wrote:
> On 04/24/2017 09:12 AM, Simon Horman wrote:
>
>>> Here's the set of 3 patches against Simon Horman's 'renesas.git' repo,
>>> 'renesas-devel-20170420-v4.11-rc7' tag. We're adding the R8A7743 PFC
>>> node
>>> and then describing the pins for SCIF0 and Ether devices declared
>>> earlier.
>>> These patches depend on the R8A7743 PFC suport in order to work properly.
>>
>>
>> Thanks. I have marked these as deferred pending acceptance of the PFC
>> driver changes. Please repost or otherwise let me know when dependency
>> is satisfied.
>
> FYI, Linus W. has pulled the R8A774x PFC patches for 4.13:
>
> https://www.spinics.net/lists/linux-renesas-soc/msg14824.html
But Simon has to wait for v4.13-rc1 to apply the DTS parts, to avoid
regressions in renesas/devel.
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert at linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
next prev parent reply other threads:[~2017-06-07 17:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-20 18:51 [PATCH v2 0/3] Add R8A7743/SK-RZG1M PFC support Sergei Shtylyov
2017-04-24 6:12 ` Simon Horman
2017-06-07 16:16 ` Sergei Shtylyov
2017-06-07 17:52 ` Geert Uytterhoeven [this message]
2017-06-08 12:53 ` Sergei Shtylyov
2017-07-05 10:33 ` Simon Horman
2017-07-05 12:06 ` Sergei Shtylyov
2017-07-05 13:10 ` 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=CAMuHMdUDO-+F_fOf4Z1ZPdZhs_MBn8J6ig-Pn4K0oMvv-EM2gw@mail.gmail.com \
--to=geert@linux-m68k.org \
--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).