From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: Wolfram Sang <wsa@the-dreams.de>
Cc: Guenter Roeck <linux@roeck-us.net>,
Jean Delvare <jdelvare@suse.com>,
Wim Van Sebroeck <wim@linux-watchdog.org>,
Martin Volf <martin.volf.42@gmail.com>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Jarkko Nikula <jarkko.nikula@linux.intel.com>,
linux-i2c@vger.kernel.org, linux-hwmon@vger.kernel.org,
linux-watchdog@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/3] i2c: i801: Fix iTCO_wdt resource creation if PMC is not present
Date: Mon, 2 Mar 2020 12:12:10 +0200 [thread overview]
Message-ID: <20200302101210.GW2667@lahna.fi.intel.com> (raw)
In-Reply-To: <20200228170342.GC1130@ninjato>
On Fri, Feb 28, 2020 at 06:03:42PM +0100, Wolfram Sang wrote:
> On Wed, Feb 26, 2020 at 04:21:19PM +0300, Mika Westerberg wrote:
> > Hi all,
> >
> > This series aims to fix the issue reported by Martin Volf [1] that prevents
> > the nct6775 driver from loading.
> >
> > I added Fixes tag to the last patch but not stable tag because the other
> > two patches it depends are not really stable material IMO. Please let me
> > know if there is a better way to organize these :)
> >
> > I tested this on Intel Whiskey Lake based system (CNL derived) and on Comet
> > Lake-V based system (SPT derived and the iTCO_wdt still works and I can see
> > the expected resources in /proc/ioports and /proc/iomem.
> >
> > The previous version of the patch series can be found here:
> >
> > https://lore.kernel.org/linux-hwmon/20200225123802.88984-1-mika.westerberg@linux.intel.com/
> >
> > Changes from the previous version:
> >
> > * Call request_region() also for iTCO_vendorsupport
> > * Drop the core populating ICH_RES_IO_SMI completely from i2c-i801.c
> >
> > [1] https://lore.kernel.org/linux-hwmon/CAM1AHpQ4196tyD=HhBu-2donSsuogabkfP03v1YF26Q7_BgvgA@mail.gmail.com/
>
> I can take this series via I2C. Just wanted to let you know that I am
> aiming for rc5, because I'd like to have this in linux-next for a week
> to make sure we don't regress again (despite all precautions) somewhere
> else.
Makes sense, thanks!
prev parent reply other threads:[~2020-03-02 10:12 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-26 13:21 [PATCH v2 0/3] i2c: i801: Fix iTCO_wdt resource creation if PMC is not present Mika Westerberg
2020-02-26 13:21 ` [PATCH v2 1/3] watchdog: iTCO_wdt: Export vendorsupport Mika Westerberg
2020-02-26 13:32 ` Guenter Roeck
2020-02-26 13:39 ` Mika Westerberg
2020-03-10 9:30 ` Wolfram Sang
2020-02-26 13:21 ` [PATCH v2 2/3] watchdog: iTCO_wdt: Make ICH_RES_IO_SMI optional Mika Westerberg
2020-02-26 13:33 ` Guenter Roeck
2020-03-10 9:30 ` Wolfram Sang
2020-02-26 13:21 ` [PATCH v2 3/3] i2c: i801: Do not add ICH_RES_IO_SMI for the iTCO_wdt device Mika Westerberg
2020-02-26 13:31 ` Guenter Roeck
2020-03-10 9:31 ` Wolfram Sang
2020-02-28 17:03 ` [PATCH v2 0/3] i2c: i801: Fix iTCO_wdt resource creation if PMC is not present Wolfram Sang
2020-03-02 10:12 ` Mika Westerberg [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=20200302101210.GW2667@lahna.fi.intel.com \
--to=mika.westerberg@linux.intel.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=jarkko.nikula@linux.intel.com \
--cc=jdelvare@suse.com \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=martin.volf.42@gmail.com \
--cc=wim@linux-watchdog.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).