From: kgene.kim@samsung.com (Kukjin Kim)
To: linux-arm-kernel@lists.infradead.org
Subject: Merge request of s5pc210 universal board.
Date: Fri, 06 Aug 2010 20:57:27 +0900 [thread overview]
Message-ID: <00ac01cb355e$8d745340$a85cf9c0$%kim@samsung.com> (raw)
In-Reply-To: <AANLkTi=dXStOUc7z5sDvPKRH4tAWbKLteqZFAzGxjUjz@mail.gmail.com>
Kyungmin Park wrote:
>
> On Fri, Aug 6, 2010 at 4:22 PM, Kyungmin Park <kmpark@infradead.org>
wrote:
> > On Fri, Aug 6, 2010 at 4:11 PM, Kukjin Kim <kgene.kim@samsung.com>
wrote:
> >> Kyungmin Park wrote:
> >>>
> >>> On Fri, Aug 6, 2010 at 1:47 PM, Kyungmin Park <kmpark@infradead.org>
> >> wrote:
> >>> > On Fri, Aug 6, 2010 at 1:43 PM, Kukjin Kim <kgene.kim@samsung.com>
> >> wrote:
> >>> >> Kyungmin Park wrote:
> >>> >>>
> >>> >>> Dear all,
> >>> >>>
> >>> >> Hi,
> >>> >>
> >>> >>> Now I checked the next-v310 tree and know that only LSI required
codes
> >>> >>> are merged.
> >>> >>> http://git.kernel.org/?p=linux/kernel/git/kgene/linux-
> >>> >>> samsung.git;a=shortlog;h=refs/heads/next-s5pv310
> >>> >>>
> >>> >>> I can't find any reason to omit the universal board file. It's
posted
> >>> >>> before merge window and no difference with LSI SMDK board at
current
> >>> >>> status.
> >>> >>
> >>> >> Please answer my concern..I already replied to you about this.
> >>> >>
> >>> >>
> >>
http://lists.infradead.org/pipermail/linux-arm-kernel/2010-July/022087.html
> >>> >> ---
> >>> >>> >> +config MACH_UNIVERSAL
> >>> >>> >
> >>> >>> > As I still asking, do you _really_ want to use 'UNIVERSAL' as
the
> >>> >>> > board(machine) name?
> >>> >>>
> >>> >>> Yes, it's called 'universal' and it's really universal board at
here.
> >>> >>> I don't confuse the engineer who develop this board.
> >>> >>> Maybe your engineers saw and hear the brief description about
> >> universal
> >>> >> board.
> >>> >>>
> >>> >> Actually, I know that. But there are S5PC100, S5PC110 universal
board
> >>> >> also...
> >>> >> So I asked to you that you _really_ want to use 'universal'
here...and
> >> I'm
> >>> >> still concerning.
> >>> >
> >>> > No comment means "Of course want to merge it". thank you for your
> >>> > concerning. but I can handle it.
> >>>
> >> Hi,
> >>
> >>> After discuss with Mr. Kim. I changed to use non-generic name to
> >> universal_c210.
> >>>
> >> Thanks for your understanding...IMHO, 'MACH_UNIVERSAL_C210' is quite
> long...
> >> If you don't mind, how about 'MACH_UNI_C210' or 'MACH_UNIC210'...but it
> >> depends on your decision.
> >
> > FYI: These are also candidates but my team voted and decide to use it.
> >
> >>
> >>> Then do you resend the patch? or can you handle it by yourself?
> >>>
> >> I will apply this with changing it.
> Please modify the machine ID only. I want to use the universal prefix
> at variables as is.
>
Ah...just now submitted with changing every stuff...
..ok...will update it ;-)
> Thank you,
> Kyungmin Park
> > Thanks
> >>
> >>> To Russell.
> >>> Sorry for bothering you.
> >>> Can you change the registered universal to universal_c210?
> >>> universal_c210 ? ? ? ? ?MACH_UNIVERSAL_C210 ? ? UNIVERSAL_C210
>
> >>>
> >>> Thank you,
> >>> Kyungmin Park
> >>> >
> >>> >> ---
> >>> >>
> >>> >>> I try to support our board at mainline kernel but it seems to make
a
> >>> >>> difficult with unknown commit criteria of LSI.
> >>> >>>
> >>> >>
> >>
Thanks.
Best regards,
Kgene.
--
Kukjin Kim <kgene.kim@samsung.com>, Senior Engineer,
SW Solution Development Team, Samsung Electronics Co., Ltd.
prev parent reply other threads:[~2010-08-06 11:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-06 4:35 Merge request of s5pc210 universal board Kyungmin Park
2010-08-06 4:43 ` Kukjin Kim
2010-08-06 4:47 ` Kyungmin Park
2010-08-06 6:24 ` Kyungmin Park
2010-08-06 7:11 ` Kukjin Kim
2010-08-06 7:22 ` Kyungmin Park
2010-08-06 11:53 ` Kyungmin Park
2010-08-06 11:57 ` 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='00ac01cb355e$8d745340$a85cf9c0$%kim@samsung.com' \
--to=kgene.kim@samsung.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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;
as well as URLs for NNTP newsgroup(s).