From: Timur Tabi <timur@codeaurora.org>
To: Mika Westerberg <mika.westerberg@linux.intel.com>,
Wolfram Sang <wsa@the-dreams.de>
Cc: Austin Christ <austinwc@codeaurora.org>,
linux-arm-msm@vger.kernel.org, rruigrok@codeaurora.org,
linux-kernel@vger.kernel.org, nkaje@codeaurora.org,
cov@codeaurora.org, linux-arm-kernel@lists.infradead.org,
linux-i2c@vger.kernel.org
Subject: Re: [PATCH v4 1/2] i2c: qup: add ACPI support
Date: Mon, 20 Jun 2016 10:00:46 -0500 [thread overview]
Message-ID: <5768051E.3020008@codeaurora.org> (raw)
In-Reply-To: <20160620082420.GX1739@lahna.fi.intel.com>
Mika Westerberg wrote:
> Use has_acpi_companion() if you need to.
Is has_acpi_companion() the preferred alternative to ACPI_HANDLE()? We
frequently need to write code that does something different on ACPI vs
DT, and there doesn't appear to be much consistency on how that's handled.
--
Sent by an employee of the Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the
Code Aurora Forum, hosted by The Linux Foundation.
next prev parent reply other threads:[~2016-06-20 15:00 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-08 18:19 [PATCH v4 1/2] i2c: qup: add ACPI support Austin Christ
2016-06-08 18:19 ` [PATCH v4 2/2] i2c: qup: support SMBus block read Austin Christ
2016-06-18 14:13 ` Wolfram Sang
2016-06-08 21:02 ` [PATCH v4 1/2] i2c: qup: add ACPI support Arnd Bergmann
2016-06-30 11:35 ` Christopher Covington
2016-06-30 11:52 ` Arnd Bergmann
2016-06-30 18:50 ` Christopher Covington
2016-07-01 9:57 ` Arnd Bergmann
2016-06-09 13:51 ` kbuild test robot
2016-06-18 14:10 ` Wolfram Sang
2016-06-20 8:24 ` Mika Westerberg
2016-06-20 15:00 ` Timur Tabi [this message]
2016-06-20 15:07 ` Mika Westerberg
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=5768051E.3020008@codeaurora.org \
--to=timur@codeaurora.org \
--cc=austinwc@codeaurora.org \
--cc=cov@codeaurora.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
--cc=nkaje@codeaurora.org \
--cc=rruigrok@codeaurora.org \
--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).