From: Jarkko Nikula <jarkko.nikula@linux.intel.com>
To: William Breathitt Gray <william.gray@linaro.org>,
Randy Dunlap <rdunlap@infradead.org>,
Bartosz Golaszewski <brgl@bgdev.pl>,
Jonathan Cameron <jic23@kernel.org>
Cc: linux-iio@vger.kernel.org,
Linus Walleij <linus.walleij@linaro.org>,
Lars-Peter Clausen <lars@metafoo.de>,
linux-kernel@vger.kernel.org, linux-gpio@vger.kernel.org,
andy.shevchenko@gmail.com
Subject: Re: [PATCH] counter: Fix menuconfig "Counter support" submenu entries disappearance
Date: Wed, 21 Jun 2023 10:04:10 +0300 [thread overview]
Message-ID: <99948b63-1f12-e9b6-11a2-e564f47b94f0@linux.intel.com> (raw)
In-Reply-To: <ZJIWLYtl6BEHfDZQ@fedora>
On 6/21/23 00:12, William Breathitt Gray wrote:
> On Tue, Jun 20, 2023 at 02:00:37PM -0700, Randy Dunlap wrote:
>> Hi,
>>
>> On 6/20/23 10:01, William Breathitt Gray wrote:
>>> The current placement of the I8254 Kconfig entry results in the
>>> disappearance of the "Counter support" submenu items in menuconfig. Move
>>> the I8254 above the menuconfig COUNTER entry to restore the intended
>>> submenu behavior.
>>>
>>> Fixes: d428487471ba ("counter: i8254: Introduce the Intel 8254 interface library module")
>>> Reported-by: Jarkko Nikula <jarkko.nikula@linux.intel.com>
>>> Closes: https://lore.kernel.org/all/32ddaa7b-53a8-d61f-d526-b545bd561337@linux.intel.com/
>>> Signed-off-by: William Breathitt Gray <william.gray@linaro.org>
>>
>> Reviewed-by: Randy Dunlap <rdunlap@infradead.org>
>>
Thanks, this fixes it.
Tested-by: Jarkko Nikula <jarkko.nikula@linux.intel.com>
Reviewed-by: Jarkko Nikula <jarkko.nikula@linux.intel.com>
next prev parent reply other threads:[~2023-06-21 7:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-20 17:01 [PATCH] counter: Fix menuconfig "Counter support" submenu entries disappearance William Breathitt Gray
2023-06-20 21:00 ` Randy Dunlap
2023-06-20 21:12 ` William Breathitt Gray
2023-06-21 7:04 ` Jarkko Nikula [this message]
2023-06-25 11:11 ` Jonathan Cameron
2023-06-26 22:19 ` William Breathitt Gray
2023-06-21 18:25 ` 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=99948b63-1f12-e9b6-11a2-e564f47b94f0@linux.intel.com \
--to=jarkko.nikula@linux.intel.com \
--cc=andy.shevchenko@gmail.com \
--cc=brgl@bgdev.pl \
--cc=jic23@kernel.org \
--cc=lars@metafoo.de \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=william.gray@linaro.org \
/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.