linux-kernel - RE: Re: [PATCH v4 4/4] PM: Devfreq: Add Exynos5-bus devfreq driver for Exynos5250

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Wed, 03 Apr 2013 13:35:18 +0900
From:	Kukjin Kim <kgene.kim@...sung.com>
To:	'Abhilash Kesavan' <kesavan.abhilash@...il.com>,
	myungjoo.ham@...sung.com
Cc:	linux-kernel@...r.kernel.org, linux-pm@...r.kernel.org,
	'박경민' <kyungmin.park@...sung.com>,
	rjw@...k.pl,
	'최종환' <jhbird.choi@...sung.com>
Subject: RE: Re: [PATCH v4 4/4] PM: Devfreq: Add Exynos5-bus devfreq driver for
 Exynos5250

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

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/