linux-i2c.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jarkko Nikula <jarkko.nikula@linux.intel.com>
To: Phil Reid <preid@electromag.com.au>,
	andriy.shevchenko@linux.intel.com,
	mika.westerberg@linux.intel.com, wsa@the-dreams.de,
	linux-i2c@vger.kernel.org, sfr@canb.auug.org.au
Subject: Re: [PATCH 2/2] i2c: designware: fix building driver as module
Date: Tue, 28 Nov 2017 10:58:28 +0200	[thread overview]
Message-ID: <a8423851-ab3d-7274-3c36-4043d368b36a@linux.intel.com> (raw)
In-Reply-To: <1511838551-4035-3-git-send-email-preid@electromag.com.au>

On 11/28/2017 05:09 AM, Phil Reid wrote:
> The designware core and platform are built as separate modules.
> Export i2c_dw_prepare_clk() so it can be used by the platform
> driver.
> 
> Fixes commit a34a0b6da22540d19e57
> ("i2c: designware: move i2c_dw_plat_prepare_clk to common")
> 
> Signed-off-by: Phil Reid <preid@electromag.com.au>
> ---
>   drivers/i2c/busses/i2c-designware-common.c | 1 +
>   1 file changed, 1 insertion(+)
> 
> diff --git a/drivers/i2c/busses/i2c-designware-common.c b/drivers/i2c/busses/i2c-designware-common.c
> index 6b82809..27ebd90 100644
> --- a/drivers/i2c/busses/i2c-designware-common.c
> +++ b/drivers/i2c/busses/i2c-designware-common.c
> @@ -197,6 +197,7 @@ int i2c_dw_prepare_clk(struct dw_i2c_dev *dev, bool prepare)
>   	clk_disable_unprepare(dev->clk);
>   	return 0;
>   }
> +EXPORT_SYMBOL_GPL(i2c_dw_prepare_clk);
>   
Acked-by: Jarkko Nikula <jarkko.nikula@linux.intel.com>

  reply	other threads:[~2017-11-28  8:58 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-28  3:09 [PATCH 0/2] i2c: fix compile failures Phil Reid
2017-11-28  3:09 ` [PATCH 1/2] i2c: core: fix compile issue related to incorrect gpio header Phil Reid
2017-11-28  9:04   ` Jarkko Nikula
2017-11-28  9:48   ` Wolfram Sang
2017-11-28  3:09 ` [PATCH 2/2] i2c: designware: fix building driver as module Phil Reid
2017-11-28  8:58   ` Jarkko Nikula [this message]
2017-11-28  9:48   ` Wolfram Sang

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=a8423851-ab3d-7274-3c36-4043d368b36a@linux.intel.com \
    --to=jarkko.nikula@linux.intel.com \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=linux-i2c@vger.kernel.org \
    --cc=mika.westerberg@linux.intel.com \
    --cc=preid@electromag.com.au \
    --cc=sfr@canb.auug.org.au \
    --cc=wsa@the-dreams.de \
    /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).