From: Randy Dunlap <rdunlap@xenotime•net>
To: Stephen Rothwell <sfr@canb•auug.org.au>,
Thomas Mingarelli <thomas.mingarelli@hp•com>
Cc: linux-next@vger•kernel.org, LKML <linux-kernel@vger•kernel.org>,
Wim Van Sebroeck <wim@iguana•be>,
linux-watchdog@vger•kernel.org
Subject: Re: linux-next: Tree for July 27 (watchdog/hpwdt)
Date: Wed, 27 Jul 2011 09:41:12 -0700 [thread overview]
Message-ID: <20110727094112.89ab9901.rdunlap@xenotime.net> (raw)
In-Reply-To: <20110727141151.d31e3da6a8d21a255473293c@canb.auug.org.au>
On Wed, 27 Jul 2011 14:11:51 +1000 Stephen Rothwell wrote:
> Hi all,
>
> Just in case anyone needs reminding: Please do not add anything destined
> for v3.2 into linux-next included trees until after v3.1-rc1.
When CONFIG_HPWDT_NMI_DECODING is not enabled:
drivers/watchdog/hpwdt.c:833: error: 'allow_kdump' undeclared (first use in this function)
drivers/watchdog/hpwdt.c:833: error: 'priority' undeclared (first use in this function)
---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
next prev parent reply other threads:[~2011-07-27 16:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-27 4:11 linux-next: Tree for July 27 Stephen Rothwell
2011-07-27 16:27 ` [patch] Re: linux-next: Tree for July 27 (misc/pti) Randy Dunlap
2011-07-27 18:54 ` J Freyensee
2011-07-27 16:41 ` Randy Dunlap [this message]
2011-07-27 19:39 ` linux-next: Tree for July 27 (watchdog/hpwdt) Wim Van Sebroeck
2011-07-27 17:11 ` [PATCH -next] firmware: fix google/gsmi.c build warning Randy Dunlap
2011-07-27 19:49 ` Mike Waychison
2011-07-27 18:42 ` [PATCH -next] tpm_tis: fix build when ACPI is not enabled Randy Dunlap
2011-08-03 18:56 ` Ingo Molnar
2011-08-04 1:34 ` James Morris
[not found] ` <20110727104716.dda819dc.rdunlap@xenotime.net>
2011-07-27 20:11 ` linux-next: Tree for July 27 (iscsi_target) [resend/lost] Nicholas A. Bellinger
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=20110727094112.89ab9901.rdunlap@xenotime.net \
--to=rdunlap@xenotime$(echo .)net \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=linux-watchdog@vger$(echo .)kernel.org \
--cc=sfr@canb$(echo .)auug.org.au \
--cc=thomas.mingarelli@hp$(echo .)com \
--cc=wim@iguana$(echo .)be \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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