From: Andrew Benton <b3nton@gmail.com>
To: Jan Beulich <JBeulich@novell.com>
Cc: Sam Ravnborg <sam@ravnborg.org>, Michal Marek <mmarek@suse.cz>,
linux-kbuild <linux-kbuild@vger.kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] fixes for using make 3.82
Date: Mon, 16 Aug 2010 14:17:35 +0100 [thread overview]
Message-ID: <4C693A6F.4000501@gmail.com> (raw)
In-Reply-To: <4C6942D102000078000100C9@vpn.id2.novell.com>
On 16/08/10 12:53, Jan Beulich wrote:
>>>> On 16.08.10 at 13:41, Sam Ravnborg<sam@ravnborg.org> wrote:
>> Added: Michael Marek (kbuild maintainer) + linux-kbuild.
>>
>> I assume this fixes firmware build reported by Andrew Benton (cc:ed).
>
> Yes, it does (I had observed the same, which prompted the fix).
>
I can confirm that the patch fixes the problem, I can compile the kernel
with make-3.82.
Many thanks.
Andy
next prev parent reply other threads:[~2010-08-16 13:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-16 10:58 [PATCH] fixes for using make 3.82 Jan Beulich
2010-08-16 11:41 ` Sam Ravnborg
2010-08-16 11:53 ` Jan Beulich
2010-08-16 11:53 ` Jan Beulich
2010-08-16 13:17 ` Andrew Benton [this message]
2010-08-17 9:50 ` Michal Marek
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=4C693A6F.4000501@gmail.com \
--to=b3nton@gmail.com \
--cc=JBeulich@novell.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mmarek@suse.cz \
--cc=sam@ravnborg.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.