From: Kukjin Kim <kgene.kim@samsung.com>
To: 'Abhilash Kesavan' <kesavan.abhilash@gmail.com>,
myungjoo.ham@samsung.com
Cc: linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org,
'박경민' <kyungmin.park@samsung.com>,
rjw@sisk.pl, '최종환' <jhbird.choi@samsung.com>
Subject: RE: Re: [PATCH v4 4/4] PM: Devfreq: Add Exynos5-bus devfreq driver for Exynos5250
Date: Wed, 03 Apr 2013 13:35:18 +0900 [thread overview]
Message-ID: <24d701ce3024$a52d5310$ef87f930$%kim@samsung.com> (raw)
In-Reply-To: <CAM4voakFpXwG7ukO5p4=NKDQZc--rcLDPU8jGag_gB=4ZdvRAA@mail.gmail.com>
Abhilash Kesavan wrote:
> >> > One concern is that I cannot apply Patch 1/4 directly as the .dts
> file isn't
> >> > available to me.
> >> > Do you intend to apply that patch to another tree and apply the other
> three
> >> > to devfreq tree?
> >> I have been merging the devfreq tree into Kgene's tree for my testing.
> I am not
> >> sure how this should get in, any suggestions ?
> >
> > I'd suggest to send Patch 1/4 to Kgene and get it applied first if that
> patch is preliminary to the other patchset. If it is not, we can go
> seperated and independently.
> Thanks for the suggestion. Kgene is a recipient on patches 1 and 2. I
> am hoping he'll pick it up soon. However, the devfreq patches are not
> dependent on them and can be applied independently.
Just note, as I commented, arch side patches should be re-worked and
current devfreq in mainline won't cause any problems without the arch side.
And I discussed with Abhilash about that, he will finish arch side re-
posting next time.
Thanks.
- Kukjin
prev parent reply other threads:[~2013-04-03 4:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-04 8:19 Re: [PATCH v4 4/4] PM: Devfreq: Add Exynos5-bus devfreq driver for Exynos5250 MyungJoo Ham
2013-02-04 8:31 ` Abhilash Kesavan
2013-04-03 4:35 ` Kukjin Kim [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='24d701ce3024$a52d5310$ef87f930$%kim@samsung.com' \
--to=kgene.kim@samsung.com \
--cc=jhbird.choi@samsung.com \
--cc=kesavan.abhilash@gmail.com \
--cc=kyungmin.park@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=myungjoo.ham@samsung.com \
--cc=rjw@sisk.pl \
/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