linux-i2c.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Wolfram Sang <wsa@the-dreams.de>
To: Charles Keepax <ckeepax@opensource.cirrus.com>
Cc: mika.westerberg@linux.intel.com, jarkko.nikula@linux.intel.com,
	andriy.shevchenko@linux.intel.com, linux-i2c@vger.kernel.org,
	linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org,
	benjamin.tissoires@redhat.com, jbroadus@gmail.com,
	patches@opensource.cirrus.com
Subject: Re: [PATCH v7 0/6] I2C IRQ Probe Improvements
Date: Sat, 29 Jun 2019 13:29:22 +0200	[thread overview]
Message-ID: <20190629112921.GE1685@kunai> (raw)
In-Reply-To: <20190626150302.22703-1-ckeepax@opensource.cirrus.com>

[-- Attachment #1: Type: text/plain, Size: 1145 bytes --]

On Wed, Jun 26, 2019 at 04:02:56PM +0100, Charles Keepax wrote:
> This series attempts to align as much IRQ handling into the
> probe path as possible. Note that I don't have a great setup
> for testing these patches so they are mostly just build tested
> and need careful review and testing before any of them are
> merged.
> 
> The series brings the ACPI path inline with the way the device
> tree path handles the IRQ entirely at probe time. However,
> it still leaves any IRQ specified through the board_info as
> being handled at device time. In that case we need to cache
> something from the board_info until probe time, which leaves
> any alternative solution with something basically the same as
> the current handling although perhaps caching more stuff.

Ehrm, I somehow lost the cover-letter from v8, so I am replying here.
Sorry for the noise.

So, since all patches have the review from Mika and Andy (thanks!), I
applied v8 now to for-next. I had a glimpse, too, and thought it was
ready to go. But I didn't really review myself, I trust you guys. Thank
you, Charles, for your efforts working on this one!


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

      parent reply	other threads:[~2019-06-29 11:29 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-26 15:02 [PATCH v7 0/6] I2C IRQ Probe Improvements Charles Keepax
2019-06-26 15:02 ` [PATCH v7 1/6] i2c: core: Allow whole core to use i2c_dev_irq_from_resources Charles Keepax
2019-06-26 15:02 ` [PATCH v7 2/6] i2c: acpi: Use available IRQ helper functions Charles Keepax
2019-06-26 19:09   ` Andy Shevchenko
2019-06-27  8:18     ` Charles Keepax
2019-06-26 15:02 ` [PATCH v7 3/6] i2c: acpi: Factor out getting the IRQ from ACPI Charles Keepax
2019-06-26 15:03 ` [PATCH v7 4/6] i2c: core: Move ACPI IRQ handling to probe time Charles Keepax
2019-06-26 15:03 ` [PATCH v7 5/6] i2c: core: Move ACPI gpio IRQ handling into i2c_acpi_get_irq Charles Keepax
2019-06-26 15:03 ` [PATCH v7 6/6] i2c: core: Tidy up handling of init_irq Charles Keepax
2019-06-26 19:11 ` [PATCH v7 0/6] I2C IRQ Probe Improvements Andy Shevchenko
2019-06-29 11:29 ` 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=20190629112921.GE1685@kunai \
    --to=wsa@the-dreams.de \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=benjamin.tissoires@redhat.com \
    --cc=ckeepax@opensource.cirrus.com \
    --cc=jarkko.nikula@linux.intel.com \
    --cc=jbroadus@gmail.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mika.westerberg@linux.intel.com \
    --cc=patches@opensource.cirrus.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).