From: Wolfram Sang <wsa-dev@sang-engineering.com>
To: Austin Christ <austinwc@codeaurora.org>
Cc: wsa@the-dreams.de, linux-arm-msm@vger.kernel.org,
timur@codeaurora.org, linux-kernel@vger.kernel.org,
rruigrok@codeaurora.org, nkaje@codeaurora.org,
linux-i2c@vger.kernel.org, sricharan@codeaurora.org,
linux-arm-kernel@lists.infradead.org, cov@codeaurora.org
Subject: Re: [v6,1/2] i2c: qup: add ACPI support
Date: Tue, 29 Nov 2016 22:46:00 +0100 [thread overview]
Message-ID: <20161129214600.GA23045@katana> (raw)
In-Reply-To: <1476203277-6893-2-git-send-email-austinwc@codeaurora.org>
[-- Attachment #1.1: Type: text/plain, Size: 422 bytes --]
On Tue, Oct 11, 2016 at 10:27:56AM -0600, Austin Christ wrote:
> From: Naveen Kaje <nkaje@codeaurora.org>
>
> Add support to get the device parameters from ACPI. Assume
> that the clocks are managed by firmware.
>
> Signed-off-by: Naveen Kaje <nkaje@codeaurora.org>
> Signed-off-by: Austin Christ <austinwc@codeaurora.org>
> Reviewed-by: Sricharan R <sricharan@codeaurora.org>
Applied to for-next, thanks!
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
[-- Attachment #2: Type: text/plain, Size: 176 bytes --]
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2016-11-29 21:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-11 16:27 [PATCH v6 0/2] Add ACPI support and SMBus block read Austin Christ
2016-10-11 16:27 ` [PATCH v6 1/2] i2c: qup: add ACPI support Austin Christ
2016-11-29 21:46 ` Wolfram Sang [this message]
2016-10-11 16:27 ` [PATCH v6 2/2] i2c: qup: support SMBus block read Austin Christ
2016-11-29 21:46 ` [v6,2/2] " 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=20161129214600.GA23045@katana \
--to=wsa-dev@sang-engineering.com \
--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=nkaje@codeaurora.org \
--cc=rruigrok@codeaurora.org \
--cc=sricharan@codeaurora.org \
--cc=timur@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).