From: Wolfram Sang <wsa@the-dreams.de>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: Mika Westerberg <mika.westerberg@linux.intel.com>,
Jarkko Nikula <jarkko.nikula@linux.intel.com>,
linux-i2c@vger.kernel.org
Subject: Re: [PATCH v1 1/1] i2c: designware-pci: use IRQF_COND_SUSPEND flag
Date: Tue, 26 Jan 2016 07:01:59 +0100 [thread overview]
Message-ID: <20160126060159.GE1533@katana> (raw)
In-Reply-To: <1452888132-134446-1-git-send-email-andriy.shevchenko@linux.intel.com>
[-- Attachment #1: Type: text/plain, Size: 857 bytes --]
On Fri, Jan 15, 2016 at 10:02:12PM +0200, Andy Shevchenko wrote:
> This is effectively reapplies the commit b0898fdaffb2 (i2c: designware-pci: use
> IRQF_COND_SUSPEND flag) after the commit d80d134182ba (i2c: designware: Move
> common probe code into i2c_dw_probe()). Original message as follows.
>
> The mentioned flag fixes a warning on Intel Edison board since one of the I2C
> controller shares IRQ line with watchdog timer.
>
> Fixes: d80d134182ba (i2c: designware: Move common probe code into i2c_dw_probe())
> Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Fixed this checkpatch error:
ERROR: Please use git commit description style 'commit <12+ chars of sha1> ("<title line>")' - ie: 'commit d80d134182ba ("i2c: designware: Move common probe code into i2c_dw_probe()")'
and applied to for-current, thanks!
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
prev parent reply other threads:[~2016-01-26 6:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-15 20:02 [PATCH v1 1/1] i2c: designware-pci: use IRQF_COND_SUSPEND flag Andy Shevchenko
2016-01-18 6:51 ` Jarkko Nikula
2016-01-26 6:01 ` Wolfram Sang [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=20160126060159.GE1533@katana \
--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 \
/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).