From: "Gabor Z. Papp" <gzp@papp.hu>
To: Greg KH <gregkh@suse.de>
Cc: linux-kernel@vger.kernel.org, stable@kernel.org,
stable-review@kernel.org
Subject: Re: [0/6] 2.6.27.52 stable review [try 3]
Date: Thu, 19 Aug 2010 03:18:51 +0200 [thread overview]
Message-ID: <x6d3tfh01w@gzp> (raw)
In-Reply-To: 20100818150615.GA4752@kroah.com
* Greg KH <gregkh@suse.de>:
| Here's the 3rd try for the 2.6.27.52 kernel release. It has 3 more
| patches than the -rc1 release, and two more than -rc2.
What about this?
kbuild: fix make incompatibility
author Sam Ravnborg <sam@ravnborg.org>
Sat, 13 Dec 2008 22:00:45 +0000 (23:00 +0100)
committer Sam Ravnborg <sam@ravnborg.org>
Sat, 13 Dec 2008 22:00:45 +0000 (23:00 +0100)
commit 31110ebbec8688c6e9597b641101afc94e1c762a
tree 208aaad7e40cbb86bc125760664911da8cd4eebb tree | snapshot
parent abf681ce5b6f83f0b8883e0f2c12d197a38543dd commit | diff
kbuild: fix make incompatibility
"Paul Smith" <psmith@gnu.org> reported that we would fail to build
with a new check that may be enabled in an upcoming version of make.
The error was:
Makefile:442: *** mixed implicit and normal rules. Stop.
next prev parent reply other threads:[~2010-08-19 1:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-18 15:06 [0/6] 2.6.27.52 stable review [try 3] Greg KH
2010-08-18 15:01 ` [1/6] mm: keep a guard page below a grow-down stack segment Greg KH
2010-08-18 15:01 ` [2/6] mm: fix missing page table unmap for stack guard page failure case Greg KH
2010-08-18 15:01 ` [3/6] x86: dont send SIGBUS for kernel page faults Greg KH
2010-08-18 15:01 ` [4/6] mm: pass correct mm when growing stack Greg KH
2010-08-18 15:01 ` [5/6] mm: fix page table unmap for stack guard page properly Greg KH
2010-08-18 15:02 ` [6/6] mm: fix up some user-visible effects of the stack guard page Greg KH
2010-08-19 1:18 ` Gabor Z. Papp [this message]
2010-08-19 14:24 ` [stable] [0/6] 2.6.27.52 stable review [try 3] Greg KH
2010-08-23 22:44 ` Greg KH
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=x6d3tfh01w@gzp \
--to=gzp@papp.hu \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=stable-review@kernel.org \
--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 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.