public inbox for linuxppc-dev@ozlabs.org 
 help / color / mirror / Atom feed
From: Chen Gang <gang.chen@asianux•com>
To: "Rafael J. Wysocki" <rafael.j.wysocki@intel•com>
Cc: Greg KH <gregkh@linuxfoundation•org>,
	jacob.jun.pan@linux•intel.com,
	"linuxppc-dev@lists•ozlabs.org" <linuxppc-dev@lists•ozlabs.org>,
	srinivas.pandruvada@linux•intel.com
Subject: Re: [Suggestion] drivers: powercap: 'dev_attrs' has already removed from 'struct class'
Date: Fri, 01 Nov 2013 09:28:20 +0800	[thread overview]
Message-ID: <527303B4.2030301@asianux.com> (raw)
In-Reply-To: <52728461.2080901@intel.com>

On 11/01/2013 12:25 AM, Rafael J. Wysocki wrote:
> On 10/31/2013 3:18 AM, Chen Gang wrote:
>> Hello Maintainers
>>
>> It is removed by "bcc8edb driver core: remove dev_attrs from struct
>> class" in Oct 5 2013. But "75d2364 PowerCap: Add class driver" still
>> use it in Oct 11 2013.
>>
>> The related error (for powerpc with allmodconfig):
>>
>>    CC      drivers/powercap/powercap_sys.o
>> drivers/powercap/powercap_sys.c:484:2: error: unknown field
>> �dev_attrs� specified in initializer
>> drivers/powercap/powercap_sys.c:484:2: warning: initialization from
>> incompatible pointer type [enabled by default]
>> drivers/powercap/powercap_sys.c:484:2: warning: (near initialization
>> for �powercap_class.suspend�) [enabled by default]
>>
>>
>> Please give a check thanks.
> 
> That should have been fixed in the current linux-next already.
> 

OK, thanks.

> Thanks,
> Rafael
> 
> 
> 


-- 
Chen Gang

      reply	other threads:[~2013-11-01  1:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-31  2:18 [Suggestion] drivers: powercap: 'dev_attrs' has already removed from 'struct class' Chen Gang
2013-10-31 16:25 ` Rafael J. Wysocki
2013-11-01  1:28   ` Chen Gang [this message]

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=527303B4.2030301@asianux.com \
    --to=gang.chen@asianux$(echo .)com \
    --cc=gregkh@linuxfoundation$(echo .)org \
    --cc=jacob.jun.pan@linux$(echo .)intel.com \
    --cc=linuxppc-dev@lists$(echo .)ozlabs.org \
    --cc=rafael.j.wysocki@intel$(echo .)com \
    --cc=srinivas.pandruvada@linux$(echo .)intel.com \
    /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