From: Chris Wright <chrisw@sous-sol.org>
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: Rob Landley <rob@landley.net>, Greg KH <gregkh@suse.de>,
Samuel Masham <samuel.masham@gmail.com>,
stable@kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [stable] 2.6.24.3 broke "make headers_install".
Date: Sun, 16 Mar 2008 21:04:21 -0700 [thread overview]
Message-ID: <20080317040421.GU4416@sequoia.sous-sol.org> (raw)
In-Reply-To: <20080316151426.4b4baf09.randy.dunlap@oracle.com>
* Randy Dunlap (randy.dunlap@oracle.com) wrote:
> Yes, it's been reported a few times already and should be fixed/reverted
> in the next stable release.
Yup, fix is queued up.
thanks,
-chris
prev parent reply other threads:[~2008-03-17 4:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-25 1:36 2.6.24 patches for mips qemu target needed for stable Samuel Masham
2008-02-25 2:08 ` Ralf Baechle
2008-02-25 5:31 ` Rob Landley
2008-03-11 2:13 ` Samuel Masham
2008-03-11 3:33 ` Greg KH
2008-03-16 22:09 ` 2.6.24.3 broke "make headers_install" Rob Landley
2008-03-16 22:14 ` Randy Dunlap
2008-03-17 4:04 ` Chris Wright [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=20080317040421.GU4416@sequoia.sous-sol.org \
--to=chrisw@sous-sol.org \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=randy.dunlap@oracle.com \
--cc=rob@landley.net \
--cc=samuel.masham@gmail.com \
--cc=stable@kernel.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