From: gregkh@linuxfoundation.org (Greg KH)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] module: use a macro instead of platform_driver_register
Date: Sat, 25 May 2013 05:22:40 -0700 [thread overview]
Message-ID: <20130525122240.GC3746@kroah.com> (raw)
In-Reply-To: <51A040D2.20708@huawei.com>
On Sat, May 25, 2013 at 12:40:50PM +0800, Libo Chen wrote:
>
> I found a lot of mistakes using struct platform_driver without owner
> so I make a macro instead of the function platform_driver_register.
> It can set owner in it, then guys don`t care about module owner again.
>
> Signed-off-by: Libo Chen <libo.chen@huawei.com>
Nice job, that's the better way to fix this, I'll queue it up for 3.11.
thanks,
greg k-h
WARNING: multiple messages have this Message-ID (diff)
From: Greg KH <gregkh@linuxfoundation.org>
To: Libo Chen <clbchenlibo.chen@huawei.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
stern@rowland.harvard.edu, linux-arm-kernel@lists.infradead.org,
Li Zefan <lizefan@huawei.com>, David Miller <davem@davemloft.net>
Subject: Re: [PATCH] module: use a macro instead of platform_driver_register
Date: Sat, 25 May 2013 05:22:40 -0700 [thread overview]
Message-ID: <20130525122240.GC3746@kroah.com> (raw)
In-Reply-To: <51A040D2.20708@huawei.com>
On Sat, May 25, 2013 at 12:40:50PM +0800, Libo Chen wrote:
>
> I found a lot of mistakes using struct platform_driver without owner
> so I make a macro instead of the function platform_driver_register.
> It can set owner in it, then guys don`t care about module owner again.
>
> Signed-off-by: Libo Chen <libo.chen@huawei.com>
Nice job, that's the better way to fix this, I'll queue it up for 3.11.
thanks,
greg k-h
next prev parent reply other threads:[~2013-05-25 12:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-25 4:40 [PATCH] module: use a macro instead of platform_driver_register Libo Chen
2013-05-25 4:40 ` Libo Chen
2013-05-25 12:22 ` Greg KH [this message]
2013-05-25 12:22 ` Greg KH
2013-05-28 7:42 ` Libo Chen
2013-05-28 7:42 ` Libo Chen
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=20130525122240.GC3746@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=linux-arm-kernel@lists.infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.