All of lore.kernel.org
 help / color / mirror / Atom feed
From: kgene.kim@samsung.com (Kukjin Kim)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] samsung: fixes for v3.1-rc1
Date: Sat, 13 Aug 2011 13:04:03 +0900	[thread overview]
Message-ID: <000601cc596e$0ba61490$22f23db0$%kim@samsung.com> (raw)
In-Reply-To: <201108121758.01077.arnd.bergmann@linaro.org>

Arnd Bergmann wrote:
> 
> On Thursday 11 August 2011, Kukjin Kim wrote:
> > >   Linux 3.1-rc1 (2011-08-07 18:23:30 -0700)
> > >
> > > are available in the git repository at:
> > >   git://git.infradead.org/users/kmpark/linux-2.6-samsung for-arnd
> > >
> 
> > No, if above is required, I think, this should be handled from me not
you.
> >
> > Don't make a complete confusion between your board and Samsung
architecture
> > maintainer.
> 
> I'll hold off on pulling this one then until I get another pull request
> from you.
> 
> Looking at the contents of the branch, I noticed that it's not clear why
> they are needed in 3.1. It would help me if you (whoever sends me the bug
> fixes) can categorize them in the changelog:
> 
> * Any bug fixes against old bugs should be marked 'Cc: stable at kernel.org'
> so that they can get identified for backports.
> 
> * Regressions against the 3.0 kernel should get marked as such.
> 
> * Bug fixes against new code should also be identified as such.
> 
OK, I see.

As a note, I will send Samsung fixes in the beginning of next week.

Thanks.

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

  reply	other threads:[~2011-08-13  4:04 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-11  6:58 [GIT PULL] samsung: fixes for v3.1-rc1 Kyungmin Park
2011-08-11  7:11 ` Kukjin Kim
2011-08-12 15:58   ` Arnd Bergmann
2011-08-13  4:04     ` Kukjin Kim [this message]
2011-08-17  5:54       ` Kyungmin Park
2011-08-19  5:24         ` Kukjin Kim

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='000601cc596e$0ba61490$22f23db0$%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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.