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: [GIT PULL] Samsung Fixes for v3.1-rc7
Date: Sat, 17 Sep 2011 10:02:38 +0900	[thread overview]
Message-ID: <00d701cc74d5$7f302720$7d907560$%kim@samsung.com> (raw)
In-Reply-To: <20110916134300.GB16280@suse.de>

Greg KH wrote:
> 
> On Fri, Sep 16, 2011 at 08:50:51PM +0900, Kukjin Kim wrote:
> > Arnd Bergmann wrote:
> > >
> > > On Thursday 15 September 2011, Kukjin Kim wrote:
> > > > This is Samsung fixes for v3.1
> > > >
> > > > Please pull from:
> > > >   git://github.com/kgene/linux-samsung.git samsung-fixes-2
> > > > As you know, git.kernel.org/master.kernel.org has been down so I use
> > > > temporary git repo. at github now.
> > > >
> > > > These things are needed for v3.1 and if any problems, please let me
> > know.
> > > >
> > > > As a note, others for v3.2 will be sent in the next week...
> > >
> > > Thanks, pulled.
> > >
> > > Is it correct that you want none of these patches to be backported
> > > into the stable or longterm releases? Some of these look like they
> > > should be marked 'Cc: stable at kernel.org'.
> > >
> > (Cc'ed Greg K-H)
> >
> > Yes, you're right. Some patches are needed to sent to stable at kernel.org.
> > But unfortunately, when they have been submitted, there was no 'Cc:
> > stable at kernel.org'...
> 
> What do you mean?  Do you mean you just forgot to add them, or you
> created them so long ago before there was a stable at kernel.org?
> 
I mean I didn't add them before sending 'pull request' during -rc :(

> > In this case, I'm not sure which following method is proper...
> > - to send 'pull request' to Greg / stable at kernel.org like bug fix during
-rc
> > - to submit each patches with adding 'Cc: stable at kernel.org' again
> > - or ?
> 
> Are these in Linus's tree already?  If so, send me the git commit ids
> and I will add them to the stable kernels.
> 
In this case, not yet. But there are some bug fixing patches which have been
accepted in mainline not in stable.

> If not, wait until they are, and then send me the git commit ids, and I
> will then add them.
> 
OK, let you know what git commit is needed to apply into stable.

> Before they get to Linus, there's nothing I can do with them, and I
> don't accept pull requests as that makes no sense when it comes to the
> stable kernel patch flow.
> 
OK, I didn't know about the stable kernel patch flow exactly.

> Does this help?
> 
Sure, thank you so much.
Have a nice weekend :)

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

      parent reply	other threads:[~2011-09-17  1:02 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-15  9:56 [GIT PULL] Samsung Fixes for v3.1-rc7 Kukjin Kim
2011-09-15 15:32 ` Arnd Bergmann
2011-09-16 11:50   ` Kukjin Kim
2011-09-16 13:43     ` Greg KH
2011-09-16 16:34       ` Arnd Bergmann
2011-09-17  1:08         ` Kukjin Kim
2011-09-17  8:47           ` Arnd Bergmann
2011-09-17  1:02       ` 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='00d701cc74d5$7f302720$7d907560$%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).