From: Tony Lindgren <tony@atomide.com>
To: Dirk Behme <dirk.behme@googlemail.com>
Cc: linux-omap-open-source@linux.omap.com
Subject: Re: Pending December (January) patches
Date: Wed, 10 Jan 2007 11:17:20 -0800 [thread overview]
Message-ID: <20070110191720.GG3219@atomide.com> (raw)
In-Reply-To: <45A51EC9.50007@googlemail.com>
Hi,
* Dirk Behme <dirk.behme@googlemail.com> [070110 09:14]:
> Tony Lindgren wrote:
> >These should be applied now, everybody please check your patches got
> >applied OK.
>
> Except the two patches which need update our pending patches
> list is now empty :) Thanks!
:)
> What do you think about preparing stuff for 2.6.21 upstream
> merge window now? 2.6.20-rc4 is there and it looks like this
> is a calmer release, maybe 2.6.20 is coming in time.
Yes, I'll update that probably next week so we'll be ready well
ahead.
> I think frist we should remove our old stuff from RMKs patch
> tracking system. It is still in incoming state [1]. Then
> send the updates so RMK can early comment on it. With some
> luck we hit the 2.6.21-rc1 window.
I agree. If we have conflicting patches, it may cause some delays
getting the big patch set applied. I just marked the previous core
omap patches as superceded.
Does anybody have bug fixes that should go to mainline before
the big merge? If there aren't any urgent ones, I suggest we
wait for 2.6.20 to make the big merge easier.
> Tony: Not sure about your current workload, maybe people can
> help?
>
> All: Opinions?
I've scheduled some time for this and the patch queue is now pretty
easy to update. Also I've scripted out some parts :) So I think we're
in good shape for sending out the core omap patches.
Where people can help is picking an individual driver subsystem to
clean up for sending it upstream.
Imre will be sending out the framebuffer patches when he has a chance.
But at least sound and v4l driver code should be cleaned up and
sent upstream.
Anybody interested in working on merging audio and/or v4l?
Regards,
Tony
> [1]
> http://www.arm.linux.org.uk/developer/patches/section.php?section=0
prev parent reply other threads:[~2007-01-10 19:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-05 15:33 Pending December (January) patches Dirk Behme
2007-01-06 7:08 ` Komal Shah
2007-01-09 23:59 ` Tony Lindgren
2007-01-10 17:13 ` Dirk Behme
2007-01-10 19:17 ` Tony Lindgren [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=20070110191720.GG3219@atomide.com \
--to=tony@atomide.com \
--cc=dirk.behme@googlemail.com \
--cc=linux-omap-open-source@linux.omap.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox