From: Greg KH <gregkh@suse.de>
To: Wanlong Gao <wanlong.gao@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] C2port:Fix deprecated exported interfaces c2port.h
Date: Thu, 5 May 2011 07:10:24 -0700 [thread overview]
Message-ID: <20110505141024.GA6461@suse.de> (raw)
In-Reply-To: <1304598549-3561-1-git-send-email-wanlong.gao@gmail.com>
On Thu, May 05, 2011 at 08:29:09PM +0800, Wanlong Gao wrote:
> From: Wanlong Gao <wanlong.gao@gmail.com>
>
> Change to_class_dev to to_device since the struct class_device had
> merged to struct device.
> Fix the to_c2port_device interface since the struct c2port_device
> has no member named class.
>
> Signed-off-by: Wanlong Gao <wanlong.gao@gmail.com>
> ---
> include/linux/c2port.h | 4 ++--
I don't know why you sent this to me, have you looked at the
scripts/get_maintainer.pl tool?
> 1 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/include/linux/c2port.h b/include/linux/c2port.h
> index 2a5cd86..7e6bd33 100644
> --- a/include/linux/c2port.h
> +++ b/include/linux/c2port.h
> @@ -60,8 +60,8 @@ struct c2port_ops {
> * Exported functions
> */
>
> -#define to_class_dev(obj) container_of((obj), struct class_device, kobj)
> -#define to_c2port_device(obj) container_of((obj), struct c2port_device, class)
> +#define to_device(obj) container_of(obj, struct device, kobj)
> +#define to_c2port_device(obj) container_of(obj, struct c2port_device, dev.kobj)
Doesn't this break the build? If not, something is really wrong here.
confused,
greg k-h
next prev parent reply other threads:[~2011-05-05 14:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-05 12:29 [PATCH] C2port:Fix deprecated exported interfaces c2port.h Wanlong Gao
2011-05-05 14:10 ` Greg KH [this message]
2011-05-05 14:30 ` Wanlong Gao
2011-05-05 14:39 ` Greg KH
2011-05-05 14:54 ` Wanlong Gao
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=20110505141024.GA6461@suse.de \
--to=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=wanlong.gao@gmail.com \
/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