linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Greg KH <greg@kroah.com>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
	Andi Kleen <andi@firstfloor.org>
Subject: Re: linux-next: driver-core tree build warning
Date: Wed, 20 Jan 2010 17:44:41 +1100	[thread overview]
Message-ID: <20100120174441.e1b12fd7.sfr@canb.auug.org.au> (raw)
In-Reply-To: <20100120172543.e884a8af.sfr@canb.auug.org.au>

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

Hi Greg,

On Wed, 20 Jan 2010 17:25:43 +1100 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> (lines 262-266)
> static struct sysdev_class_attribute *cpu_sysdev_class_attrs[] = {
> #ifdef CONFIG_ARCH_CPU_PROBE_RELEASE
>         &class_attr_probe.attr,
>         &class_attr_release.attr,
> #endif

The reason you may not see this is because CONFIG_ARCH_CPU_PROBE_RELEASE
is not set for x86_64 allmodconfig builds (and probably many others).

-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/

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

  reply	other threads:[~2010-01-20  6:44 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-19  6:27 linux-next: driver-core tree build warning Stephen Rothwell
2010-01-19 21:04 ` Greg KH
2010-01-19 23:45   ` Stephen Rothwell
2010-01-20  6:25     ` Stephen Rothwell
2010-01-20  6:44       ` Stephen Rothwell [this message]
2010-01-21 23:10         ` Greg KH
2010-01-21 23:20           ` Stephen Rothwell
2010-01-29  7:21           ` Stephen Rothwell
2010-02-03  2:22             ` Greg KH
2010-02-03  3:29               ` Stephen Rothwell
2010-02-04  7:10               ` Stephen Rothwell
  -- strict thread matches above, loose matches on Subject: below --
2009-07-13  7:26 Stephen Rothwell
2009-07-13  7:28 ` Stephen Rothwell
2009-07-13  7:51   ` Stephen Rothwell
2009-07-13 17:18     ` Greg KH
2009-07-13 21:23       ` David Brownell
2009-07-13 21:27         ` Greg KH
2009-07-13 21:36         ` Greg KH
2009-07-14  0:44           ` Stephen Rothwell
2009-05-01  5:21 Stephen Rothwell
     [not found] ` <20090501152144.500e619a.sfr-3FnU+UHB4dNDw9hX6IcOSA@public.gmane.org>
2009-05-01  5:47   ` Greg KH
2009-05-01  6:11     ` Greg KH
2009-05-01  7:11       ` Stephen Rothwell
2008-08-15  2:59 Stephen Rothwell
2008-08-16  5:34 ` Greg KH
2008-08-18 19:09   ` Jason Baron
2008-08-18 22:35     ` 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=20100120174441.e1b12fd7.sfr@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=andi@firstfloor.org \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@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).