From: Wolfram Sang <wsa@the-dreams.de>
To: Hans de Goede <hdegoede@redhat.com>
Cc: Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Mika Westerberg <mika.westerberg@linux.intel.com>,
Sebastian Reichel <sre@kernel.org>,
linux-acpi@vger.kernel.org, Takashi Iwai <tiwai@suse.de>,
linux-pm@vger.kernel.org
Subject: Re: [PATCH v3 3/4] i2c: core: Allow drivers to specify index for irq to get from of / ACPI
Date: Thu, 30 Mar 2017 22:39:54 +0200 [thread overview]
Message-ID: <20170330203954.GA1452@katana> (raw)
In-Reply-To: <1935239d-fdd8-3917-9865-de389e6728e8@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 759 bytes --]
Hi Hans,
> Sorry for doing this in the middle of the thread, but this is the only
> mail I could find in my archives (I guess I delete mail to aggressively).
I use patchwork to track patches (which is mentioned in MAINTAINERS).
And patchwork has the nice feature to download patches or series of
patches as mbox. And from there you can reply directly, or bounce to
yourself first, etc. That's what I do when I lost a mail.
> Anyways self-nack for this series, there are multiple issues with it:
>
> 1) In hindsight the irq_index is a bad idea and instead we need a noirq
> flag in i2c_driver
What do you mean by that? No IRQ assigned? In Linux, 0 is no irq. I
guess you mean something else...
Thanks for the heads up,
Wolfram
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2017-03-30 20:39 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-25 13:55 [PATCH v3 0/4]: i2c-core improvements for complex ACPI-devices + cht-wc-fuel-gauge driver Hans de Goede
2017-03-25 13:55 ` [PATCH v3 1/4] i2c: core: Allow getting ACPI info by index Hans de Goede
2017-03-26 12:16 ` Andy Shevchenko
2017-03-25 13:55 ` [PATCH v3 2/4] i2c: core: Add new i2c_acpi_new_device helper function Hans de Goede
2017-03-25 13:55 ` [PATCH v3 3/4] i2c: core: Allow drivers to specify index for irq to get from of / ACPI Hans de Goede
2017-03-26 12:15 ` Andy Shevchenko
2017-03-26 15:07 ` Hans de Goede
2017-03-30 17:39 ` Hans de Goede
2017-03-30 20:39 ` Wolfram Sang [this message]
2017-03-31 10:03 ` Hans de Goede
2017-03-31 16:23 ` Wolfram Sang
2017-03-31 18:22 ` Hans de Goede
2017-03-31 19:54 ` Wolfram Sang
2017-03-31 20:13 ` Andy Shevchenko
2017-03-31 20:59 ` Hans de Goede
2017-03-31 21:19 ` Wolfram Sang
2017-04-01 16:33 ` Dmitry Torokhov
2017-04-02 12:17 ` Hans de Goede
2017-04-03 18:29 ` Dmitry Torokhov
2017-03-25 13:55 ` [PATCH v3 4/4] power: supply: Add driver for Cherry Trail Whiskey Cove PMIC Fuel Gauge Hans de Goede
2017-03-25 18:42 ` Sebastian Reichel
2017-03-26 8:56 ` Hans de Goede
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=20170330203954.GA1452@katana \
--to=wsa@the-dreams.de \
--cc=andriy.shevchenko@linux.intel.com \
--cc=hdegoede@redhat.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
--cc=sre@kernel.org \
--cc=tiwai@suse.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).