Linux I2C development
 help / color / mirror / Atom feed
From: Wolfram Sang <wsa@the-dreams.de>
To: Phil Reid <preid@electromag.com.au>
Cc: jarkko.nikula@linux.intel.com, andriy.shevchenko@linux.intel.com,
	mika.westerberg@linux.intel.com, linux-i2c@vger.kernel.org,
	sfr@canb.auug.org.au
Subject: Re: [PATCH 1/2] i2c: core: fix compile issue related to incorrect gpio header
Date: Tue, 28 Nov 2017 10:48:33 +0100	[thread overview]
Message-ID: <20171128094833.vwxplzbzzrnu6uch@ninjato> (raw)
In-Reply-To: <1511838551-4035-2-git-send-email-preid@electromag.com.au>

[-- Attachment #1: Type: text/plain, Size: 603 bytes --]

On Tue, Nov 28, 2017 at 11:09:10AM +0800, Phil Reid wrote:
> The correct header to include for the gpiod interface is
> <linux/gpio/consumer.h>.
> 
> fixes commit 3991c5c80beaf7eb9 ("i2c: Switch to using gpiod interface
> for gpio bus recovery")

Thanks for the fixes tag, yet please use this format in the future:

Fixes: <sha> ("desc")

like

Fixes: a34a0b6da22540d19e57 ("i2c: designware: move i2c_dw_plat_prepare_clk to common")

Fixed it myself for these two patches.


> Signed-off-by: Phil Reid <preid@electromag.com.au>

Applied to for-next, thanks for the fast reaction!


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  parent reply	other threads:[~2017-11-28  9:48 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 [this message]
2017-11-28  3:09 ` [PATCH 2/2] i2c: designware: fix building driver as module Phil Reid
2017-11-28  8:58   ` Jarkko Nikula
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=20171128094833.vwxplzbzzrnu6uch@ninjato \
    --to=wsa@the-dreams.de \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=jarkko.nikula@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 \
    /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