On Mon, May 6, 2013 at 4:26 PM, Dave Jones davej@redhat.com wrote:
On Mon, May 06, 2013 at 09:13:30PM +0100, Peter Robinson wrote:
On Mon, May 6, 2013 at 9:07 PM, Dave Jones davej@redhat.com wrote:
On Thu, May 02, 2013 at 02:02:12PM -0400, Josh Boyer wrote:
I would feel extremely bad if I pushed something to git that didn't even pass 'make prep'. As a compromise, I added this line in kernel.spec:
@@ -1451,6 +1451,8 @@ mkdir configs rm -f kernel-%{version}-*debug.config %endif
+rm -f kernel-%{version}-arm*.config
# now run oldconfig over all the config files
So the ARM configs won't be included in the prep run. That lets things progress on all the other arches for now. Just remove that line, fix things up, and push out.
FYI, I've just done the same thing in f18 during the 3.9 rebase. I don't see us pushing this out until 3.9.1 lands, but please sort out the config options there too.
Thanks, I'll look at it now, for <= F-18 we still support v5tel so I need to deal with that.
Any idea on eta for 3.9.1?
Probably sometime this week I would guess. There's already over a hundred patches queued on Linux-stable for 3.9
Greg typically seems to wait until Linus tags rc1, so whenever the merge window closes, you can probably expect 3.9.1 to land pretty soon afterwards.
I'm kinda hesitant on that plan. We seem to always pull in some patches from -rc1 that wind up being broken and fixed with a later RC, or reverted outright. Of course, there isn't a great answer there but maybe we can bump the karma requirement up when the update is filed?
josh