From: Kukjin Kim <kgene.kim@samsung.com>
To: "'Kyungmin Park'" <kmpark@infradead.org>
Cc: "'Linus Torvalds'" <torvalds@linux-foundation.org>,
linux-samsung-soc@vger.kernel.org, ben-linux@fluff.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: RE: [GIT PULL] Samsung fixes for 2.6.36-rc3
Date: Sun, 29 Aug 2010 18:43:25 +0900 [thread overview]
Message-ID: <000101cb475e$a364eef0$ea2eccd0$%kim@samsung.com> (raw)
In-Reply-To: <AANLkTi=+XnCQu6Cz0P+A=qhaeN2HKJ9gYdTx2jWe7sfH@mail.gmail.com>
Kyungmin Park wrote:
>
> On Fri, Aug 27, 2010 at 6:48 PM, Kukjin Kim <kgene.kim@samsung.com> wrote:
> > Hi Linus,
> >
> > Please pull Samsung fixes from:
> >
> > git://git.kernel.org/pub/scm/linux/kernel/git/kgene/linux-samsung.git
> > s5p-fixes-for-linus
> >
> > These things are for bug fix on 2.6.36-rc3.
> > If any problems, please let me know.
>
> Well nothing changed. only LSI codes and required things from LSI side
> are merged.
At this point, focus on getting the critical portions of S5PV310/S5PC210
into
the mainline. Once that is done, other features can be merged as required.
> And still need more patches for booting at s5pc210 (aka s5pv310).
>
Thanks for your concern.
But I think it's enough just only one patch about following...
I know the problem that we cannot get the proper clock 'id' from clk_get()
in
the console_initcall(). This problem occurs when only defined 'uclk1' as
uart
clock. And to solve that will be submitted soon.
> Several thins are missed.
> 1. gpio_to_irq patch not included. it's basic gpiolib feature. Without
> this patch, it can't use the generic gpiolib based drivers. e.g.,
> gpio-keys.
> http://marc.info/?l=linux-arm-kernel&m=128202435823832&w=2
>
I don't think so, 'gpio_to_irq' is a new feature not a bug fix.
So if required, will be merged at the merge window after review.
> 2. Wrong UART level triggers.
> At least s5pc110/s5pc210 has wrong UART trigger values compare to macro
name.
> http://marc.info/?l=linux-arm-kernel&m=128218476209330&w=2
>
I couldn't find anywhere used it in the mainline. So I'm not sure we really
need it.
> 3. set correct gpio config at GPIO I at s5pc110
> http://marc.info/?l=linux-arm-kernel&m=128202423923745&w=2
>
mm...I will sort this out.
(snip)
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-29 9:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-27 9:48 Kukjin Kim
2010-08-28 5:55 ` Kyungmin Park
2010-08-29 9:43 ` 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='000101cb475e$a364eef0$ea2eccd0$%kim@samsung.com' \
--to=kgene.kim@samsung.com \
--cc=ben-linux@fluff.org \
--cc=kmpark@infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=torvalds@linux-foundation.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
Powered by JetHome