On Mon, May 6, 2013 at 10:07 PM, Dave Jones davej@redhat.com wrote:
On Mon, May 06, 2013 at 04:26:52PM -0400, Dave Jones 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.
And just after I posted that he posted 3.9.1-rc1 with the comment..
"Responses should be made by Wed May 8 20:28:24 UTC 2013."
I'll roll the rc1 into git after dinner to get some testing, but I won't be pushing out an update until later in the week.
I've pushed the 3.9 ARM config changes to the F-18 branch, it passes make prep and the allarchconfig.sh config script, I'll do a scratch build but that should stop ARM from blocking the rebase. Thanks
Peter
-
Peter Robinson