From: Jean Delvare <jdelvare@suse.de>
To: linux-sh@vger.kernel.org
Subject: Re: R-CAR's arch
Date: Fri, 23 May 2014 08:52:06 +0000 [thread overview]
Message-ID: <1400835126.4451.18.camel@chaos.site> (raw)
In-Reply-To: <20140522101938.51fec16f@endymion.delvare>
Le Friday 23 May 2014 à 10:39 +0200, Geert Uytterhoeven a écrit :
> Hi Jean,
>
> On Fri, May 23, 2014 at 10:23 AM, Jean Delvare <jdelvare@suse.de> wrote:
> > For USB PHY the dependencies are clear. For VIN I'm not so sure, does
> > anybody know? I'd got for ARCH_SHMOBILE || COMPILE_TEST but I don't know
> > if SUPERH should be listed too.
>
> R-Car falls under shmobile (which also covers Emma Mobile and R-Mobile).
> I.e. no SUPERH.
OK. Patch written and sent, thanks!
--
Jean Delvare
SUSE L3 Support
next prev parent reply other threads:[~2014-05-23 8:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-22 8:19 R-CAR's arch Jean Delvare
2014-05-22 22:55 ` Laurent Pinchart
2014-05-23 0:37 ` Simon Horman
2014-05-23 8:08 ` Jean Delvare
2014-05-23 8:23 ` Jean Delvare
2014-05-23 8:39 ` Geert Uytterhoeven
2014-05-23 8:52 ` Jean Delvare [this message]
2014-05-23 11:31 ` Sergei Shtylyov
2014-05-23 11:45 ` Jean Delvare
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=1400835126.4451.18.camel@chaos.site \
--to=jdelvare@suse.de \
--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).