From: Ben Dooks <ben-linux@fluff.org>
To: Marek Szyprowski <m.szyprowski@samsung.com>
Cc: 'Ben Dooks' <ben-linux@fluff.org>,
linux-samsung-soc@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, kyungmin.park@samsung.com
Subject: Re: SAMSUNG kernel tree merge plans
Date: Mon, 10 May 2010 04:49:37 +0100 [thread overview]
Message-ID: <20100510034937.GX26401@trinity.fluff.org> (raw)
In-Reply-To: <015f01caece8$723e1700$56ba4500$%szyprowski@samsung.com>
On Thu, May 06, 2010 at 08:50:38AM +0200, Marek Szyprowski wrote:
> Hello,
>
> On Thursday, May 06, 2010 7:47 AM Ben Dooks wrote:
>
> > I'm busy sorting out the trees for the next mege window, and should
> > have a new next-samsung out in the next two or three days.
> >
> > As such, if there is anything that needs to go via Russell's tree, then
> > it needs to be merged as soon as possible. I would like to send a pull
> > before Wednesday.
> >
> > Anything else, if it is not merged into one of my trees by the end of
> > next week (May 14th) then there is no guarantees that it will be merged.
> >
> > If everyone interested in this could check my trees after the weekend and
> > make any reminders of other stuff to fix at that point as there is still
> > items being processed.
> >
> > http://git.fluff.org/gitweb?p=bjdooks/linux.git;a=summary
>
> We would really like to merge as much as possible from our current
> development tree:
> http://git.infradead.org/users/kmpark/linux-2.6-samsung/shortlog/refs/heads/SPRC-2.6.34-rc5-opensource
>
> Some of the patches that we depend on are still in the review phase (s5p timer), some should be replaced by the ones that were
> posted recently. Especially most of our patches depend on S5PV210 GPIO support, so without it we cannot go further. Is there any
> chance to get it merged quickly? I will rebase our tree asap the mentioned patches get merged.
I'll sort out what can be merged from the items on the list, but I'm
not going git-tree diving just at the moment. The firstset will be
stuff for Russell's tree, for linus' tree there is a ltitle more time
to get prepared.
--
Ben
Q: What's a light-year?
A: One-third less calories than a regular year.
WARNING: multiple messages have this Message-ID (diff)
From: ben-linux@fluff.org (Ben Dooks)
To: linux-arm-kernel@lists.infradead.org
Subject: SAMSUNG kernel tree merge plans
Date: Mon, 10 May 2010 04:49:37 +0100 [thread overview]
Message-ID: <20100510034937.GX26401@trinity.fluff.org> (raw)
In-Reply-To: <015f01caece8$723e1700$56ba4500$%szyprowski@samsung.com>
On Thu, May 06, 2010 at 08:50:38AM +0200, Marek Szyprowski wrote:
> Hello,
>
> On Thursday, May 06, 2010 7:47 AM Ben Dooks wrote:
>
> > I'm busy sorting out the trees for the next mege window, and should
> > have a new next-samsung out in the next two or three days.
> >
> > As such, if there is anything that needs to go via Russell's tree, then
> > it needs to be merged as soon as possible. I would like to send a pull
> > before Wednesday.
> >
> > Anything else, if it is not merged into one of my trees by the end of
> > next week (May 14th) then there is no guarantees that it will be merged.
> >
> > If everyone interested in this could check my trees after the weekend and
> > make any reminders of other stuff to fix at that point as there is still
> > items being processed.
> >
> > http://git.fluff.org/gitweb?p=bjdooks/linux.git;a=summary
>
> We would really like to merge as much as possible from our current
> development tree:
> http://git.infradead.org/users/kmpark/linux-2.6-samsung/shortlog/refs/heads/SPRC-2.6.34-rc5-opensource
>
> Some of the patches that we depend on are still in the review phase (s5p timer), some should be replaced by the ones that were
> posted recently. Especially most of our patches depend on S5PV210 GPIO support, so without it we cannot go further. Is there any
> chance to get it merged quickly? I will rebase our tree asap the mentioned patches get merged.
I'll sort out what can be merged from the items on the list, but I'm
not going git-tree diving just at the moment. The firstset will be
stuff for Russell's tree, for linus' tree there is a ltitle more time
to get prepared.
--
Ben
Q: What's a light-year?
A: One-third less calories than a regular year.
next prev parent reply other threads:[~2010-05-10 3:49 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-06 5:46 SAMSUNG kernel tree merge plans Ben Dooks
2010-05-06 5:46 ` Ben Dooks
2010-05-06 6:50 ` Marek Szyprowski
2010-05-06 6:50 ` Marek Szyprowski
2010-05-10 3:49 ` Ben Dooks [this message]
2010-05-10 3:49 ` Ben Dooks
2010-05-11 7:57 ` Marek Szyprowski
2010-05-11 7:57 ` Marek Szyprowski
2010-05-06 7:21 ` Vasily Khoruzhick
2010-05-06 7:21 ` Vasily Khoruzhick
2010-05-06 9:15 ` Ben Dooks
2010-05-06 9:15 ` Ben Dooks
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=20100510034937.GX26401@trinity.fluff.org \
--to=ben-linux@fluff.org \
--cc=kyungmin.park@samsung.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
/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.