From: Jonathan Cameron <jic23@kernel.org>
To: Wei Yongjun <weiyj.lk@gmail.com>
Cc: jic23@cam.ac.uk, gregkh@linuxfoundation.org,
sameo@linux.intel.com, rachna@ti.com, bigeasy@linutronix.de,
yongjun_wei@trendmicro.com.cn, linux-iio@vger.kernel.org
Subject: Re: [PATCH] iio: ti_am335x_adc: add missing .driver_module to struct iio_info
Date: Sat, 06 Jul 2013 10:37:57 +0100 [thread overview]
Message-ID: <51D7E575.40708@kernel.org> (raw)
In-Reply-To: <CAPgLHd-Y35AOCRLcjdFfoNrK9v6n7Th_gjB-GAPpwoAe81H63w@mail.gmail.com>
On 07/06/2013 05:20 AM, Wei Yongjun wrote:
> From: Wei Yongjun <yongjun_wei@trendmicro.com.cn>
>
> Add missing .driver_module of struct iio_info. This prevents the
> module from being removed from underneath its users.
>
> Signed-off-by: Wei Yongjun <yongjun_wei@trendmicro.com.cn>
Applied to the fixes-togreg branch of iio.git
Thanks,
> ---
> drivers/iio/adc/ti_am335x_adc.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/iio/adc/ti_am335x_adc.c b/drivers/iio/adc/ti_am335x_adc.c
> index 5f9a7e7..985f588 100644
> --- a/drivers/iio/adc/ti_am335x_adc.c
> +++ b/drivers/iio/adc/ti_am335x_adc.c
> @@ -134,6 +134,7 @@ static int tiadc_read_raw(struct iio_dev *indio_dev,
>
> static const struct iio_info tiadc_info = {
> .read_raw = &tiadc_read_raw,
> + .driver_module = THIS_MODULE,
> };
>
> static int tiadc_probe(struct platform_device *pdev)
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-iio" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
prev parent reply other threads:[~2013-07-06 9:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-06 4:20 [PATCH] iio: ti_am335x_adc: add missing .driver_module to struct iio_info Wei Yongjun
2013-07-06 9:37 ` Jonathan Cameron [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=51D7E575.40708@kernel.org \
--to=jic23@kernel.org \
--cc=bigeasy@linutronix.de \
--cc=gregkh@linuxfoundation.org \
--cc=jic23@cam.ac.uk \
--cc=linux-iio@vger.kernel.org \
--cc=rachna@ti.com \
--cc=sameo@linux.intel.com \
--cc=weiyj.lk@gmail.com \
--cc=yongjun_wei@trendmicro.com.cn \
/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).