From: Kevin Hilman <khilman@deeprootsystems.com>
To: Peter 'p2' De Schrijver <peter.de-schrijver@nokia.com>
Cc: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: [PATCH 1/1] per board prm timings
Date: Fri, 13 Feb 2009 11:08:08 -0800 [thread overview]
Message-ID: <87skmijgtj.fsf@deeprootsystems.com> (raw)
In-Reply-To: <20090213102430.GA4582@codecarver.research.nokia.com> (Peter De Schrijver's message of "Fri\, 13 Feb 2009 12\:24\:30 +0200")
"Peter 'p2' De Schrijver" <peter.de-schrijver@nokia.com> writes:
> Hi Kevin,
>
>> Peter,
>>
>> I like this approach much better than what we currently have. Pushing
>> to PM branch.
>>
>> The next thing I would like to see is all the register value defines
>> removed from prm-regbits-34xx.h. That header is supposed to be for
>> the bitfield definitions, not for values.
>>
>
> True. If this patch goes in, there is no need for the register value
> defines in prm-regbits-34xx.h any more.
>
OK, I pushed a patch which removes them from regbits.h and moved some of the
other value defines into pm34xx.c until a better place is found.
Kevin
next prev parent reply other threads:[~2009-02-13 19:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-10 16:04 [PATCH 0/1] Board specific prm timings Peter 'p2' De Schrijver
2009-02-10 16:04 ` [PATCH 1/1] per board " Peter 'p2' De Schrijver
2009-02-12 17:47 ` Kevin Hilman
2009-02-13 10:24 ` Peter 'p2' De Schrijver
2009-02-13 19:08 ` Kevin Hilman [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-02-05 17:38 [PATCH 0/1] Board specific " Peter 'p2' De Schrijver
2009-02-05 17:38 ` [PATCH 1/1] per board " Peter 'p2' De Schrijver
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=87skmijgtj.fsf@deeprootsystems.com \
--to=khilman@deeprootsystems.com \
--cc=linux-omap@vger.kernel.org \
--cc=peter.de-schrijver@nokia.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.