From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: William Breathitt Gray <vilhelm.gray@gmail.com>,
linus.walleij@linaro.org, linux-gpio@vger.kernel.org,
linux-arch@vger.kernel.org, linux-kernel@vger.kernel.org,
linux@rasmusvillemoes.dk
Subject: Re: [PATCH v8 0/8] Introduce the for_each_set_clump8 macro
Date: Fri, 8 Feb 2019 18:39:08 +0200 [thread overview]
Message-ID: <20190208163908.GR9224@smile.fi.intel.com> (raw)
In-Reply-To: <20190129170734.688a6adf91267cc6f1b5fa08@linux-foundation.org>
On Tue, Jan 29, 2019 at 05:07:34PM -0800, Andrew Morton wrote:
> On Mon, 14 Jan 2019 15:19:17 +0900 William Breathitt Gray <vilhelm.gray@gmail.com> wrote:
> It's a shame that it doesn't actually dercease the kernel line count,
> but there are other benefits.
>
> The patches are missing the hoped-for acks, but I think you maintain
> most/all of those drivers.
I'm okay with the code as well, so,
Reviewed-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
> Do we have any expectation that these facilities will be used by
> anything other than GPIO? If not then perhaps they should be sited
> within drivers/gpio (presumably as a standalone module) until such a
> need is found?
I think I have an example out of GPIO realm. But I need time to prove that.
In any case I tend to bend to the generic exposure than to local one.
--
With Best Regards,
Andy Shevchenko
prev parent reply other threads:[~2019-02-08 16:39 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-14 6:19 [PATCH v8 0/8] Introduce the for_each_set_clump8 macro William Breathitt Gray
2019-01-14 6:19 ` [PATCH v8 1/8] bitops: " William Breathitt Gray
2019-01-14 6:20 ` [PATCH v8 2/8] lib/test_bitmap.c: Add for_each_set_clump8 test cases William Breathitt Gray
2019-01-14 6:20 ` [PATCH v8 3/8] gpio: 104-dio-48e: Utilize for_each_set_clump8 macro William Breathitt Gray
2019-01-14 6:20 ` [PATCH v8 4/8] gpio: 104-idi-48: " William Breathitt Gray
2019-01-14 6:21 ` [PATCH v8 5/8] gpio: gpio-mm: " William Breathitt Gray
2019-01-14 6:21 ` [PATCH v8 6/8] gpio: ws16c48: " William Breathitt Gray
2019-01-14 6:21 ` [PATCH v8 7/8] gpio: pci-idio-16: " William Breathitt Gray
2019-01-14 6:22 ` [PATCH v8 8/8] gpio: pcie-idio-24: " William Breathitt Gray
2019-01-30 1:07 ` [PATCH v8 0/8] Introduce the " Andrew Morton
2019-01-30 9:44 ` Linus Walleij
2019-01-30 10:18 ` William Breathitt Gray
2019-01-30 11:56 ` Linus Walleij
2019-02-08 16:39 ` 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=20190208163908.GR9224@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=akpm@linux-foundation.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rasmusvillemoes.dk \
--cc=vilhelm.gray@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.