From: Kyle McMartin <kmcmartin@redhat.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.6.24-rc6
Date: Thu, 20 Dec 2007 21:48:05 -0500 [thread overview]
Message-ID: <20071221024805.GB8535@fattire.cabal.ca> (raw)
In-Reply-To: <alpine.LFD.0.9999.0712201731010.21557@woody.linux-foundation.org>
On Thu, Dec 20, 2007 at 05:41:09PM -0800, Linus Torvalds wrote:
> The regression list keeps shrinking, so we're still on track for a full
> 2.6.24 release in early January. Assuming we don't all overeat during the
> holidays and nobody gets any work done. But we all know that the holidays
> are really the time when we get away from the boring "real work", and can
> spend 24/7 on kernel hacking instead, right?
>
The patch-2.6.24-rc6.bz2 doesn't seem to apply to a pristine
linux-2.6.23 tree? I see this while updating Fedora:
+ '[' '!' -f /home/kyle/rpms/kernel/devel/patch-2.6.24-rc6.bz2 ']'
+ case "$patch" in
+ bunzip2
+ patch -p1 -F1 -s
1 out of 3 hunks FAILED -- saving rejects to file
drivers/video/mbx/reg_bits.h.rej
error: Bad exit status from /var/tmp/rpm-tmp.22316 (%prep)
cheers, Kyle
next prev parent reply other threads:[~2007-12-21 2:48 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-21 1:41 Linux 2.6.24-rc6 Linus Torvalds
2007-12-21 2:40 ` Zhang, Yanmin
2007-12-21 2:48 ` Kyle McMartin [this message]
2007-12-21 3:01 ` Kyle McMartin
2007-12-21 3:49 ` Linus Torvalds
2007-12-21 3:50 ` Kyle McMartin
2007-12-21 4:22 ` Linus Torvalds
2007-12-21 4:40 ` Linus Torvalds
2007-12-21 4:50 ` Kyle McMartin
2007-12-21 4:58 ` Linus Torvalds
2007-12-21 5:21 ` Linus Torvalds
2007-12-21 17:45 ` Linus Torvalds
2007-12-21 16:56 ` Junio C Hamano
2007-12-21 3:23 ` [PATCH] mbx: Fix up duplicate defines in reg_bits.h Kyle McMartin
2007-12-23 0:05 ` Linux 2.6.24-rc6 S.Çağlar Onur
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=20071221024805.GB8535@fattire.cabal.ca \
--to=kmcmartin@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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 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.