From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: William Breathitt Gray <vilhelm.gray@gmail.com>
Cc: Masahiro Yamada <yamada.masahiro@socionext.com>,
Linus Walleij <linus.walleij@linaro.org>,
Andrew Morton <akpm@linux-foundation.org>,
"open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>,
linux-arch <linux-arch@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Rasmus Villemoes <linux@rasmusvillemoes.dk>,
Bartosz Golaszewski <bgolaszewski@baylibre.com>,
Linux ARM <linux-arm-kernel@lists.infradead.org>,
Arnd Bergmann <arnd@arndb.de>
Subject: Re: [PATCH v9 1/9] bitops: Introduce the for_each_set_clump8 macro
Date: Tue, 12 Mar 2019 16:54:12 +0200 [thread overview]
Message-ID: <20190312145412.GD9224@smile.fi.intel.com> (raw)
In-Reply-To: <20190312072222.GA2898@icarus>
On Tue, Mar 12, 2019 at 04:22:22PM +0900, William Breathitt Gray wrote:
> Since Andy appears to have hardware outside of the GPIO subsystem he's
> testing, let's wait for that and see how it turns out.
Since I have still not much time, here is the driver I'm talking about
drivers/thermal/intel/intel_soc_dts_iosf.c
If you have a chance to look at it (add_dts_thermal_zone(), for example) and
prepare a patch, I will be able to test it on real hardware.
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2019-03-12 14:54 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-03 7:44 [PATCH v9 0/9] Introduce the for_each_set_clump8 macro William Breathitt Gray
2019-03-03 7:48 ` [PATCH v9 1/9] bitops: " William Breathitt Gray
2019-03-08 8:31 ` Linus Walleij
2019-03-08 8:57 ` William Breathitt Gray
2019-03-08 9:19 ` Andy Shevchenko
2019-03-12 5:36 ` Masahiro Yamada
2019-03-12 7:22 ` William Breathitt Gray
2019-03-12 14:54 ` Andy Shevchenko [this message]
2019-03-12 1:01 ` Andrew Morton
2019-03-12 10:43 ` William Breathitt Gray
2019-03-12 3:52 ` Masahiro Yamada
2019-03-12 5:03 ` Masahiro Yamada
2019-03-12 7:14 ` Andy Shevchenko
2019-03-03 7:48 ` [PATCH v9 2/9] lib/test_bitmap.c: Add for_each_set_clump8 test cases William Breathitt Gray
2019-03-11 7:56 ` [LKP] [lib/test_bitmap.c] ecdc93614a: kernel_selftests.lib.bitmap.sh.fail kernel test robot
2019-03-03 7:49 ` [PATCH v9 3/9] gpio: 104-dio-48e: Utilize for_each_set_clump8 macro William Breathitt Gray
2019-03-03 7:49 ` [PATCH v9 4/9] gpio: 104-idi-48: " William Breathitt Gray
2019-03-03 7:50 ` [PATCH v9 5/9] gpio: gpio-mm: " William Breathitt Gray
2019-03-03 7:50 ` [PATCH v9 6/9] gpio: ws16c48: " William Breathitt Gray
2019-03-03 7:51 ` [PATCH v9 7/9] gpio: pci-idio-16: " William Breathitt Gray
2019-03-03 7:51 ` [PATCH v9 8/9] gpio: pcie-idio-24: " William Breathitt Gray
2019-03-03 7:51 ` [PATCH v9 9/9] gpio: uniphier: " William Breathitt Gray
2019-03-12 4:36 ` Masahiro Yamada
2019-03-12 7:17 ` Andy Shevchenko
2019-03-12 8:57 ` Masahiro Yamada
2019-03-12 9:09 ` Andy Shevchenko
2019-03-12 7:29 ` William Breathitt Gray
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=20190312145412.GD9224@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=bgolaszewski@baylibre.com \
--cc=linus.walleij@linaro.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rasmusvillemoes.dk \
--cc=vilhelm.gray@gmail.com \
--cc=yamada.masahiro@socionext.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).