From: Olof Johansson <olof@lixom.net>
To: Kukjin Kim <kgene.kim@samsung.com>
Cc: 'Arnd Bergmann' <arnd@arndb.de>,
linux-arm-kernel@lists.infradead.org,
linux-samsung-soc@vger.kernel.org
Subject: Re: [GIT PULL 1/7] Samsung fixes for v3.7
Date: Fri, 30 Nov 2012 08:47:35 -0800 [thread overview]
Message-ID: <20121130164735.GA697@quad.lixom.net> (raw)
In-Reply-To: <1d7601cdceea$b96d7580$2c486080$%kim@samsung.com>
On Fri, Nov 30, 2012 at 08:06:19PM +0900, Kukjin Kim wrote:
> Kukjin Kim wrote:
> >
> > Hi Arnd, Olof,
> >
> Hi,
>
> > I sorted out my branches as per Olof's suggestion
> >
> I checked only merged this into arm-soc tree.
>
> Any problems on 2nd ~ 7th pull request? Or missed? ;-)
I just haven't gotten to it yet. They came in late, and it was during the time
when Stephen Rothwell got back from vacation and was dealing with a lot of
merge conflicts in linux-next. I didn't want to add anything to his load by
merging a lot of stuff the first few days.
I'll likely get to it today. And if I don't, it might not make 3.8. Those
are the risks with sending merge requests late, after all.
-Olof
WARNING: multiple messages have this Message-ID (diff)
From: olof@lixom.net (Olof Johansson)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL 1/7] Samsung fixes for v3.7
Date: Fri, 30 Nov 2012 08:47:35 -0800 [thread overview]
Message-ID: <20121130164735.GA697@quad.lixom.net> (raw)
In-Reply-To: <1d7601cdceea$b96d7580$2c486080$%kim@samsung.com>
On Fri, Nov 30, 2012 at 08:06:19PM +0900, Kukjin Kim wrote:
> Kukjin Kim wrote:
> >
> > Hi Arnd, Olof,
> >
> Hi,
>
> > I sorted out my branches as per Olof's suggestion
> >
> I checked only merged this into arm-soc tree.
>
> Any problems on 2nd ~ 7th pull request? Or missed? ;-)
I just haven't gotten to it yet. They came in late, and it was during the time
when Stephen Rothwell got back from vacation and was dealing with a lot of
merge conflicts in linux-next. I didn't want to add anything to his load by
merging a lot of stuff the first few days.
I'll likely get to it today. And if I don't, it might not make 3.8. Those
are the risks with sending merge requests late, after all.
-Olof
next prev parent reply other threads:[~2012-11-30 16:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-28 0:14 [GIT PULL 1/7] Samsung fixes for v3.7 Kukjin Kim
2012-11-28 0:14 ` Kukjin Kim
2012-11-30 11:06 ` Kukjin Kim
2012-11-30 11:06 ` Kukjin Kim
2012-11-30 16:47 ` Olof Johansson [this message]
2012-11-30 16:47 ` Olof Johansson
2012-11-30 17:36 ` Olof Johansson
2012-11-30 17:36 ` Olof Johansson
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=20121130164735.GA697@quad.lixom.net \
--to=olof@lixom.net \
--cc=arnd@arndb.de \
--cc=kgene.kim@samsung.com \
--cc=linux-arm-kernel@lists.infradead.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 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.