linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Valdis.Kletnieks@vt.edu
To: linux-kernel@vger.kernel.org
Cc: mm-commits@vger.kernel.org
Subject: Re: mmotm 2010-09-28-16-13 uploaded
Date: Tue, 28 Sep 2010 21:25:34 -0400	[thread overview]
Message-ID: <139397.1285723534@localhost> (raw)
In-Reply-To: Your message of "Tue, 28 Sep 2010 16:13:38 PDT." <201009282344.o8SNiliN024981@imap1.linux-foundation.org>

[-- Attachment #1: Type: text/plain, Size: 1169 bytes --]

On Tue, 28 Sep 2010 16:13:38 PDT, akpm@linux-foundation.org said:
> The mm-of-the-moment snapshot 2010-09-28-16-13 has been uploaded to
> 
>    http://userweb.kernel.org/~akpm/mmotm/

Also needs this from Randy Dunlap:

From: Randy Dunlap <randy.dunlap@oracle.com>

Fix build error and config symbol comment:

drivers/hwmon/pkgtemp.c:413: error:'pkgtemp_cpu_notifier' undeclared (first use in this function)

Signed-off-by: Randy Dunlap <randy.dunlap@oracle.com>
---
 drivers/hwmon/pkgtemp.c |    6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

--- linux-next-20100928.orig/drivers/hwmon/pkgtemp.c
+++ linux-next-20100928/drivers/hwmon/pkgtemp.c
@@ -386,7 +386,7 @@ static int __cpuinit pkgtemp_cpu_callbac
 static struct notifier_block pkgtemp_cpu_notifier __refdata = {
 	.notifier_call = pkgtemp_cpu_callback,
 };
-#endif				/* !CONFIG_HOTPLUG_CPU */
+#endif				/* CONFIG_HOTPLUG_CPU */
 
 static int __init pkgtemp_init(void)
 {
@@ -408,9 +408,9 @@ static int __init pkgtemp_init(void)
 		err = -ENODEV;
 		goto exit_driver_unreg;
 	}
-#endif
-
+#else
 	register_hotcpu_notifier(&pkgtemp_cpu_notifier);
+#endif
 	return 0;
 
 #ifndef CONFIG_HOTPLUG_CPU


[-- Attachment #2: Type: application/pgp-signature, Size: 227 bytes --]

  parent reply	other threads:[~2010-09-29  1:25 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-28 23:13 mmotm 2010-09-28-16-13 uploaded akpm
2010-09-29  0:27 ` N.P.S. N.P.S.
2010-09-29  0:44   ` Andrew Morton
2010-09-29 12:19     ` Arnd Bergmann
2010-09-29 12:57       ` N.P.S. N.P.S.
2010-09-29  0:49   ` Valdis.Kletnieks
2010-09-29  0:57     ` N.P.S. N.P.S.
2010-09-29  1:19       ` Valdis.Kletnieks
2010-09-29  0:49 ` N.P.S. N.P.S.
2010-09-29  1:13   ` Randy Dunlap
2010-09-29  5:55     ` Andrew Morton
2010-09-29  1:25 ` Valdis.Kletnieks [this message]
2010-09-29  9:15 ` N.P.S. N.P.S.
2010-09-29 15:00   ` Randy Dunlap
2010-09-29 15:04     ` Na Pohybel
     [not found] ` <AANLkTikk+k7WJEDv9dQoJDyMdz8NCM8LOb5kW=xyWK71@mail.gmail.com>
2010-09-29  9:17   ` Fwd: " N.P.S. N.P.S.
2010-09-29 13:13 ` N.P.S. N.P.S.
2010-09-29 15:01   ` Randy Dunlap
2010-09-29 15:05     ` Na Pohybel
2010-09-30 16:59 ` Na Pohybel
2010-09-30 18:25   ` N.P.S.
2010-09-30 19:39     ` N.P.S.
2010-10-01 15:40       ` Zimny Lech
2010-10-04 13:43         ` Zimny Lech
2010-10-04 23:16       ` Andrew Morton
2010-10-04 23:33         ` Zimny Lech
2010-10-04 23:43           ` Andrew Morton
2010-10-20 21:58           ` [PATCH] Removal of duplicate includes from many files N.P.S.
2010-10-20 23:15             ` Andrew Morton
2010-10-20 23:25               ` Zimny Lech
2010-10-24  1:48           ` mmotm 2010-09-28-16-13 uploaded Maciej W. Rozycki
2010-10-05  0:46         ` Stephen Rothwell

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=139397.1285723534@localhost \
    --to=valdis.kletnieks@vt.edu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mm-commits@vger.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;
as well as URLs for NNTP newsgroup(s).