All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eduardo Valentin <eduardo.valentin@ti.com>
To: Paul Bolle <pebolle@tiscali.nl>
Cc: Eduardo Valentin <eduardo.valentin@ti.com>,
	Zhang Rui <rui.zhang@intel.com>,
	linux-pm@vger.kernel.org
Subject: Re: config SOC_DRA7XX?
Date: Tue, 16 Jul 2013 17:02:22 -0400	[thread overview]
Message-ID: <51E5B4DE.5040906@ti.com> (raw)
In-Reply-To: <1373889707.2591.31.camel@x61.thuisdomein>

[-- Attachment #1: Type: text/plain, Size: 1139 bytes --]

On 15-07-2013 08:01, Paul Bolle wrote:
> Hi Eduardo,
> 
> On Mon, 2013-07-15 at 07:37 -0400, Eduardo Valentin wrote:
>> On 14-07-2013 10:54, Paul Bolle wrote:
>>> 2) Why is this dependency on SOC_DRA7XX needed? And what would
>>> SOC_DRA7XX actually be? Some searches on the web returned nothing that
>>> could show me what it is.
>>
>> That is the config which says the kernel has the support for the DRA7XX
>> soc family. The core support didnt make for 3.11. But I had already sent
>> this code for review and merge by then. The core code can be seen here:
>> git://github.com/rrnayak/linux.git for-3.12/dra-core-data
>>
>> for instance.
> 
> I'll stop worrying about this. And unless SOC_DRA7XX still pops up in my
> list of invalid Kconfig symbols in, say, early 2014, I won't have to
> bother you again.

Thanks Paul for point me this missing part. But I believe it won't be
something to worry, yes, because Rajendra will be sending DRA7 base
support for 3.12.

> 
> Thanks!
> 
> 
> Paul Bolle
> 
> 
> 


-- 
You have got to be excited about what you are doing. (L. Lamport)

Eduardo Valentin


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 295 bytes --]

      reply	other threads:[~2013-07-16 21:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-14 14:54 config SOC_DRA7XX? Paul Bolle
2013-07-15 11:37 ` Eduardo Valentin
2013-07-15 12:01   ` Paul Bolle
2013-07-16 21:02     ` Eduardo Valentin [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=51E5B4DE.5040906@ti.com \
    --to=eduardo.valentin@ti.com \
    --cc=linux-pm@vger.kernel.org \
    --cc=pebolle@tiscali.nl \
    --cc=rui.zhang@intel.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.