mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Kukjin Kim <kgene.kim@samsung.com>
To: "'Darius Augulis'" <augulis.darius@gmail.com>, ben-linux@fluff.org
Cc: linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-samsung-soc@vger.kernel.org
Subject: RE: [GIT PULL] Samsung fixes for 2.6.37-rc4
Date: Fri, 03 Dec 2010 19:01:34 +0900	[thread overview]
Message-ID: <015301cb92d1$132c94a0$3985bde0$%kim@samsung.com> (raw)
In-Reply-To: <AANLkTinuYg2LzwZJUnpT0-b3Gi+vOJr-_fi4o874DAFG@mail.gmail.com>

Darius Augulis wrote:
> 
> Hi Ben, Kukjin,
> 
Hi Darius,
Ok...I will apply this in my tree for -next with Ben's ack.

Ben, if any problems, please let me know.

Thanks.

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

> could you please both find out who must 'handle' it?
> Do you think it's normal to force people to ping you for the same four
> lines patch for 4 months or more?
> I think, it's at least not optimal and not good for kernel development
> process.
> 
> 
> On Tue, Nov 30, 2010 at 2:23 AM, Kukjin Kim <kgene.kim@samsung.com> wrote:
> > Darius Augulis wrote:
> >>
> >> Hi Kukjin,
> >>
> > Hi,
> >
> >> you have missed "serial: samsung: fix device name" again.
> >> Please, don't forget to add it to your tree, better do it right now.
> >> Perhaps it's fifth or sixth time when remind about that...
> >>
> > I remember, I've replied about that like following.
> > Maybe you missed...
> >
> > ---
> >> you have missed "serial: samsung: fix device name" which is hanging
here
> >> for a long time and was decided to merge in 2.6.37-rc1.
> >> Please, pick it up.
> >>
> > Hmm...I thought it should be handled by Ben Dooks at that time.
> >
> > Anyway, as Ben said, I'm thinking it should be sent upstream when merge
> > window
> > even though have missed it in the last merge window.
> >
> > However, if Ben is ok to merge this during 37-rc, will merge it into
> > s5p-fixes-
> > for-linus for 37-rc.
> > ---
> >
> > But I still thinking it should be handled by Ben Dooks...
> 
> handle what? You have Ben ack to merge it. I'm confused how 'optimal'
> is development process when have to ping the same people for the same
> four lines patch for 4 months. You both  Do you think I really have to
> ask help for arm, serial or linux-stable maintainers to 'hadle' this?
> Because I gave up believing it's possible to do by samsung
> maintainers.


      reply	other threads:[~2010-12-03 10:24 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-25  4:21 Kukjin Kim
2010-11-26 18:26 ` Darius Augulis
2010-11-30  0:23   ` Kukjin Kim
2010-11-30 15:49     ` Darius Augulis
2010-12-03 10:01       ` 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='015301cb92d1$132c94a0$3985bde0$%kim@samsung.com' \
    --to=kgene.kim@samsung.com \
    --cc=augulis.darius@gmail.com \
    --cc=ben-linux@fluff.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-samsung-soc@vger.kernel.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

all inboxes | Powered by JetHome®