From: anarsoul@gmail.com (Vasily Khoruzhick)
To: linux-arm-kernel@lists.infradead.org
Subject: SAMSUNG kernel tree merge plans
Date: Thu, 6 May 2010 10:21:02 +0300 [thread overview]
Message-ID: <201005061021.06125.anarsoul@gmail.com> (raw)
In-Reply-To: <20100506054651.GL26401@trinity.fluff.org>
? ????????? ?? 6 ??? 2010 08:46:51 ????? Ben Dooks ???????:
> 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
Is there any chance that my rx1950-support patch series will be merged? I've
almost finished moving to gpiolib and can send series after this weekend. What
branch of your tree should I use as base?
Regards
Vasily
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20100506/7bd092b8/attachment.sig>
next prev parent reply other threads:[~2010-05-06 7:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-06 5:46 SAMSUNG kernel tree merge plans Ben Dooks
2010-05-06 6:50 ` Marek Szyprowski
2010-05-10 3:49 ` Ben Dooks
2010-05-11 7:57 ` Marek Szyprowski
2010-05-06 7:21 ` Vasily Khoruzhick [this message]
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=201005061021.06125.anarsoul@gmail.com \
--to=anarsoul@gmail.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).