From: daniel@0x0f.com (Daniel Palmer)
To: linux-arm-kernel@lists.infradead.org
Subject: sh-eth.c writes to non-existent register on RZ/A1
Date: Mon, 11 Jul 2016 22:03:38 +0900 [thread overview]
Message-ID: <CAFr9PX=h4ftOUu3+0fOC9VHyjQNzLVZPHj8b260G_VUCq7-8qw@mail.gmail.com> (raw)
In-Reply-To: <KL1PR06MB1749BFFCB144EE55402339968A3F0@KL1PR06MB1749.apcprd06.prod.outlook.com>
On 11 July 2016 at 21:27, Chris Brandt <Chris.Brandt@renesas.com> wrote:
> You might have better luck posting Renesas device questions to the Renesas mailing list.
>
> http://vger.kernel.org/vger-lists.html#linux-renesas-soc
Ok, I will forward my original mail there.
> It's on my list of things to do in the next couple months to push in all the RZ/A1 BSP driver changes back upstream. After I got the XIP_LINUX fixes in earlier this year, I got a bit side tracked on other projects.
I have hacked up versions of the BSP PFC, ADC, RTC, DMAC and USB
drivers running on top of 4.7rc6. :)
prev parent reply other threads:[~2016-07-11 13:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-05 17:33 sh-eth.c writes to non-existent register on RZ/A1 Daniel Palmer
2016-07-11 12:27 ` Chris Brandt
2016-07-11 13:03 ` Daniel Palmer [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='CAFr9PX=h4ftOUu3+0fOC9VHyjQNzLVZPHj8b260G_VUCq7-8qw@mail.gmail.com' \
--to=daniel@0x0f.com \
--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).