linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: kgene.kim@samsung.com (Kukjin Kim)
To: linux-arm-kernel@lists.infradead.org
Subject: Pending patches for s5pc110
Date: Fri, 11 Jun 2010 15:18:13 +0900	[thread overview]
Message-ID: <002f01cb092d$e1728c30$a457a490$%kim@samsung.com> (raw)
In-Reply-To: <AANLkTikJQnDEjVunmiCLGaVAnj5bR7JdsUZYJ9xAEdE5@mail.gmail.com>

Kyungmin Park wrote:
> 
> On Fri, Jun 11, 2010 at 2:15 PM, Ben Dooks <ben-linux@fluff.org> wrote:
> > On Fri, Jun 11, 2010 at 01:25:18PM +0900, Kyungmin Park wrote:
> >> Hi,
> >>
> >> No comments mean it's okay then we will prepare the patches to git pull.
> >
Maybe you already know no comments do not mean it's okay.

> > No. no comments means that people either haven't had time to sort
> > them out or in fact ON HOLIDAY.
> 
> but you usually missed our patches frequently. with this reason our
> patches can't merge within proper merge window.
> 
> >
> >> Thank you,
> >> Kyungmin Park
> >>
> >> On Fri, Jun 4, 2010 at 8:53 AM, Kyungmin Park <kmpark@infradead.org>
wrote:
> >> > Hi ben,
> >> >
> >> > There's some pending patches for s5pc110.
> >> > 1. aquila & goni support files.
> >
> > these two should have gone in already
> 
> I mean more aquila & goni patches. not basic support. e.g. OneNAND
> support, FB support and so on.
> >
> >> > 2. keypad
> >
> > I think kukjin has been looking at this, best check with him.
> 
> It's already discussed. do you think it needs more comments?
> 
You mean discussed to me?
Sorry, I can't remember when we discussed about that, what's my comments?

> >
> >> > 3. s3c-fb - we have to implement FIMD and MIPI interface so please
> >> > decide how to handle it.
> >
> > since we've not had any chance to discuss what is going on here
> > I can't see how we are ready to submit anything.
> 
> It's basic functionality for s3c-fb. it's required for our target and
> want to use it. even though someone don't use it.
> 
> I wonder some features are not used for other board. in this case it
> should be merged if it doesn't break any previous board. Of course
> with proper feedback. I think we answer your question doesn't it?
> 
> Thank you,
> Kyungmin Park
> 
> >
> >> > 4. etc.
> >> >
> >> > Do you want to re-post or any activities?
> >> >
> >> > Please give your plans or opinions.
> >> >
> >> > Thank you,
> >> > Kyungmin Park
> >> >
> >>


Thanks.

Best regards,
Kgene.
--
Kukjin Kim <kgene.kim@samsung.com>, Senior Engineer,
SW Solution Development Team, Samsung Electronics Co., Ltd.

  reply	other threads:[~2010-06-11  6:18 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <AANLkTil0wWSFHpwi58enMhhG7475uUmFoZG6QhRim6Xk@mail.gmail.com>
2010-06-11  4:25 ` Pending patches for s5pc110 Kyungmin Park
2010-06-11  5:15   ` Ben Dooks
2010-06-11  5:38     ` Kyungmin Park
2010-06-11  6:18       ` Kukjin Kim [this message]
2010-06-11  6:23       ` Ben Dooks
2010-06-11  7:07         ` Kyungmin Park
2010-06-11  7:54           ` Ben Dooks
2010-06-11  8:15             ` 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='002f01cb092d$e1728c30$a457a490$%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).