From: Andy Shevchenko <andriy.shevchenko-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
To: Jarkko Sakkinen
<jarkko.sakkinen-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
Cc: tpmdd-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: [PATCH v1] tpm/st33zp24: Add GPIO ACPI mapping table
Date: Thu, 16 Mar 2017 16:03:23 +0200 [thread overview]
Message-ID: <1489673003.19767.16.camel@linux.intel.com> (raw)
In-Reply-To: <20170315082828.7cuwlrcmyqwfijbo-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
On Wed, 2017-03-15 at 10:28 +0200, Jarkko Sakkinen wrote:
> On Mon, Mar 13, 2017 at 07:38:11PM +0200, Andy Shevchenko wrote:
> > In order to make GPIO ACPI library stricter prepare users of
> > gpiod_get_index() to correctly behave when there no mapping is
> > provided by firmware.
> >
> > Here we add explicit mapping between _CRS GpioIo() resources and
> > their names used in the driver.
> >
> > Signed-off-by: Andy Shevchenko <andriy.shevchenko-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
>
> Reviewed-by: Jarkko Sakkinen <jarkko.sakkinen-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
>
> I do not have means to test this though.
Thanks you, I have sent new version to address kbuild bot complain, but
I didn't apply your tag.
--
Andy Shevchenko <andriy.shevchenko-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
Intel Finland Oy
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
next prev parent reply other threads:[~2017-03-16 14:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-13 17:38 [PATCH v1] tpm/st33zp24: Add GPIO ACPI mapping table Andy Shevchenko
[not found] ` <20170313173811.21668-1-andriy.shevchenko-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
2017-03-15 8:28 ` Jarkko Sakkinen
[not found] ` <20170315082828.7cuwlrcmyqwfijbo-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2017-03-16 14:03 ` Andy Shevchenko [this message]
2017-03-15 21:21 ` Jerry Snitselaar
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=1489673003.19767.16.camel@linux.intel.com \
--to=andriy.shevchenko-vuqaysv1563yd54fqh9/ca@public.gmane.org \
--cc=jarkko.sakkinen-VuQAYsv1563Yd54FQh9/CA@public.gmane.org \
--cc=tpmdd-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
/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).