linux-gpio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Jonathan Cameron <jic23@jic23.retrosnub.co.uk>,
	Jonathan Cameron <Jonathan.Cameron@huawei.com>,
	linux-iio@vger.kernel.org, Hartmut Knaack <knaack.h@gmx.de>,
	Lars-Peter Clausen <lars@metafoo.de>,
	Peter Meerwald-Stadler <pmeerw@pmeerw.net>,
	ACPI Devel Maling List <linux-acpi@vger.kernel.org>,
	linux-gpio@vger.kernel.org,
	Mika Westerberg <mika.westerberg@linux.intel.com>
Subject: Re: [PATCH v3 2/5] iio: proximity: sx9500: Add GPIO ACPI mapping table
Date: Fri, 01 Dec 2017 14:36:28 +0200	[thread overview]
Message-ID: <1512131788.25007.535.camel@linux.intel.com> (raw)
In-Reply-To: <CACRpkdZf_O2OwK8rRnCtZ2kKADTorfD4D-ccmcnkz1Md3fJv8Q@mail.gmail.com>

On Fri, 2017-12-01 at 11:04 +0100, Linus Walleij wrote:
> On Mon, Nov 27, 2017 at 4:08 PM, Andy Shevchenko
> <andriy.shevchenko@linux.intel.com> wrote:
> > On Sat, 2017-11-25 at 14:24 +0000, Jonathan Cameron wrote:
> > > On Sun, 19 Nov 2017 15:29:34 +0000
> > > Jonathan Cameron <jic23@kernel.org> wrote:
> > > Hi Andy, any updates on the above?   I probably won't be sending
> > > a fixes pull until next weekend, but would be good to know if this
> > > should be in there or not by then!
> > 
> > Yes, as you suggested I tried to add quirks to the core, so, this
> > patch
> > will be definitely changed.
> 
> The quirks mechanics are merged to the GPIO core and an
> immutable branch is available, so Jonathan could "just" pull that in
> and apply (elegent) fixes on top. I think.

Unfortunately I didn't see any updates WRT GPIO/pin control in linux-next.
Did you synchronize repositories?

-- 
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Intel Finland Oy

      reply	other threads:[~2017-12-01 12:40 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20171103130340.42459-1-andriy.shevchenko@linux.intel.com>
2017-11-04  3:11 ` [PATCH v3 1/5] iio: proximity: sx9500: Assign interrupt from GpioIo() Jonathan Cameron
2017-11-04 10:43   ` Linus Walleij
     [not found]   ` <20171104031119.00006e56-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
2017-11-06  9:35     ` Mika Westerberg
2017-11-19 15:24       ` Jonathan Cameron
2017-11-20 10:30         ` Mika Westerberg
2017-11-25 14:28           ` Jonathan Cameron
     [not found] ` <20171103130340.42459-2-andriy.shevchenko@linux.intel.com>
     [not found]   ` <20171103130340.42459-2-andriy.shevchenko-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
2017-11-04  3:14     ` [PATCH v3 2/5] iio: proximity: sx9500: Add GPIO ACPI mapping table Jonathan Cameron
2017-11-19 15:29       ` Jonathan Cameron
2017-11-25 14:24         ` Jonathan Cameron
2017-11-27 15:08           ` Andy Shevchenko
     [not found]             ` <1511795292.25007.454.camel-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
2017-12-01 10:04               ` Linus Walleij
2017-12-01 12:36                 ` Andy Shevchenko [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=1512131788.25007.535.camel@linux.intel.com \
    --to=andriy.shevchenko@linux.intel.com \
    --cc=Jonathan.Cameron@huawei.com \
    --cc=jic23@jic23.retrosnub.co.uk \
    --cc=knaack.h@gmx.de \
    --cc=lars@metafoo.de \
    --cc=linus.walleij@linaro.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-iio@vger.kernel.org \
    --cc=mika.westerberg@linux.intel.com \
    --cc=pmeerw@pmeerw.net \
    /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).