From: Randy Dunlap <rdunlap@infradead.org>
To: Dan Carpenter <dan.carpenter@linaro.org>
Cc: linux-kernel@vger.kernel.org,
Vaibhav Hiremath <hvaibhav.linux@gmail.com>,
Johan Hovold <johan@kernel.org>, Alex Elder <elder@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
greybus-dev@lists.linaro.org, linux-staging@lists.linux.dev
Subject: Re: [PATCH] staging: greybus: arche: drop dangling Kconfig symbol
Date: Mon, 5 Jan 2026 19:16:22 -0800 [thread overview]
Message-ID: <d78259ce-8bca-418f-a4f8-87139e8d2177@infradead.org> (raw)
In-Reply-To: <aVuNzWb3TEj74t2M@stanley.mountain>
On 1/5/26 2:09 AM, Dan Carpenter wrote:
> On Tue, Dec 30, 2025 at 10:23:40AM -0800, Randy Dunlap wrote:
>>
>>
>> On 12/29/25 10:27 PM, Randy Dunlap wrote:
>>> --- linux-next-20251219.orig/drivers/staging/greybus/Kconfig
>>> +++ linux-next-20251219/drivers/staging/greybus/Kconfig
>>> @@ -206,7 +206,6 @@ endif # GREYBUS_BRIDGED_PHY
>>>
>>> config GREYBUS_ARCHE
>>> tristate "Greybus Arche Platform driver"
>>> - depends on USB_HSIC_USB3613 || COMPILE_TEST
>>> help
>>> Select this option if you have an Arche device.
OK, with just the v1 patch here, it does build without errors.
Seems like I should leave this patch as is.
CC [M] drivers/staging/greybus/arche-platform.o
CC [M] drivers/staging/greybus/arche-apb-ctrl.o
LD [M] drivers/staging/greybus/gb-arche.o
>> Perhaps I should have left COMPILE_TEST here, like:
>>
>> depends on COMPILE_TEST
>>
>> ?
>
> If we're going to do that, we should just delete it. It's been
> impossible to build for eight years.
--
~Randy
next prev parent reply other threads:[~2026-01-06 3:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-30 6:27 Randy Dunlap
2025-12-30 18:23 ` Randy Dunlap
2026-01-05 10:09 ` Dan Carpenter
2026-01-05 10:16 ` Dan Carpenter
2026-01-05 23:54 ` Randy Dunlap
2026-01-06 3:16 ` Randy Dunlap [this message]
2026-01-14 9:21 ` Johan Hovold
2026-01-15 0:28 ` Randy Dunlap
2026-01-16 10:48 ` Johan Hovold
2026-01-17 5:40 ` Randy Dunlap
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=d78259ce-8bca-418f-a4f8-87139e8d2177@infradead.org \
--to=rdunlap@infradead.org \
--cc=dan.carpenter@linaro.org \
--cc=elder@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=greybus-dev@lists.linaro.org \
--cc=hvaibhav.linux@gmail.com \
--cc=johan@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
/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
all inboxes | Powered by JetHome®