From: Kukjin Kim <kgene.kim@samsung.com>
To: 'Kyungmin Park' <kmpark@infradead.org>,
'Jaecheol Lee' <jc.lee@samsung.com>
Cc: linux-arm-kernel@lists.infradead.org,
linux-samsung-soc@vger.kernel.org, ben-linux@fluff.org,
'함명주' <myungjoo.ham@samsung.com>,
"'Andrew Morton'" <akpm@linux-foundation.org>
Subject: RE: [PATCH 0/5] ARM: S5PV210: Add support CPUFREQ for S5PV210/S5PC110
Date: Fri, 17 Sep 2010 13:24:42 +0900 [thread overview]
Message-ID: <03ca01cb5620$42a51b50$c7ef51f0$%kim@samsung.com> (raw)
In-Reply-To: <AANLkTikB288=Y8_jMXCwfsEBqwRdOTKyjMJag=SCKYdP@mail.gmail.com>
Kyungmin Park wrote:
>
> First thank you for posting the patches.
> but I'm worry about sending the same feature patches from different
divisions.
>
It doesn't matter which division it is from.
What matters is the quality of the patch.
Any patches can be submitted anytime anywhere.
> I'm not sure you're talking with kgene. but there are some codes
> posted by Mr. Ham and get feedback and reviewed with kgene.
> http://git.infradead.org/users/kmpark/linux-2.6-
> samsung/shortlog/refs/heads/cpufreq
>
> To kgene,
> One code from DMC(me), another code from System LSI(you). then which
> codes do you pick up and apply to mainline?
As I said, it is not important where it is from.
I will apply the best patch.
> and what's rules or principles?
>
The best patch will get merged.
And I think that's the purpose of mailing lists
- to put all ideas together and find the best solution.
Thanks.
Best regards,
Kgene.
--
Kukjin Kim <kgene.kim@samsung.com>, Senior Engineer,
SW Solution Development Team, Samsung Electronics Co., Ltd.
next prev parent reply other threads:[~2010-09-17 4:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-15 7:52 [PATCH 0/5] ARM: S5PV210: Add support CPUFREQ for S5PV210/S5PC110 Jaecheol Lee
2010-09-15 7:52 ` [PATCH 1/5] ARM: S5PV210: Add support DMC map_desc table Jaecheol Lee
2010-09-15 7:52 ` [PATCH 2/5] ARM: S5PV210: Add struct clk_ops for clk_fout_apll Jaecheol Lee
2010-09-15 7:52 ` [PATCH 3/5] ARM: S5PV210: Add Register definition for CMU Jaecheol Lee
2010-09-15 7:52 ` [PATCH 4/5] ARM: S5PV210: Add support CPUFREQ Jaecheol Lee
2010-09-16 0:36 ` MyungJoo Ham
2010-09-15 7:52 ` [PATCH 5/5] ARM: S5PV210: Update Kconfig and Makefile for supporting CPUFREQ driver Jaecheol Lee
2010-09-16 0:33 ` [PATCH 0/5] ARM: S5PV210: Add support CPUFREQ for S5PV210/S5PC110 Kyungmin Park
2010-09-17 4:24 ` Kukjin Kim [this message]
2010-09-17 4:30 ` Kyungmin Park
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='03ca01cb5620$42a51b50$c7ef51f0$%kim@samsung.com' \
--to=kgene.kim@samsung.com \
--cc=akpm@linux-foundation.org \
--cc=ben-linux@fluff.org \
--cc=jc.lee@samsung.com \
--cc=kmpark@infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=myungjoo.ham@samsung.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox