Re: [PATCH] event: Correct dependencies on the EVENT framework

2023-01-16 Thread Heinrich Schuchardt
On 1/16/23 21:23, Tom Rini wrote: On Mon, Jan 16, 2023 at 09:21:51PM +0100, Heinrich Schuchardt wrote: On 1/16/23 20:12, Tom Rini wrote: The event framework is just that, a framework. Enabling it by itself does nothing, so we shouldn't ask the user about it. Reword (and correct typos) around th

Re: [PATCH] event: Correct dependencies on the EVENT framework

2023-01-16 Thread Tom Rini
On Mon, Jan 16, 2023 at 09:21:51PM +0100, Heinrich Schuchardt wrote: > On 1/16/23 20:12, Tom Rini wrote: > > The event framework is just that, a framework. Enabling it by itself > > does nothing, so we shouldn't ask the user about it. Reword (and correct > > typos) around this the option and help t

Re: [PATCH] event: Correct dependencies on the EVENT framework

2023-01-16 Thread Heinrich Schuchardt
On 1/16/23 20:12, Tom Rini wrote: The event framework is just that, a framework. Enabling it by itself does nothing, so we shouldn't ask the user about it. Reword (and correct typos) around this the option and help text. This also applies to DM_EVENT and EVENT_DYNAMIC. Only EVENT_DEBUG and CMD_EV

[PATCH] event: Correct dependencies on the EVENT framework

2023-01-16 Thread Tom Rini
The event framework is just that, a framework. Enabling it by itself does nothing, so we shouldn't ask the user about it. Reword (and correct typos) around this the option and help text. This also applies to DM_EVENT and EVENT_DYNAMIC. Only EVENT_DEBUG and CMD_EVENT should be visible to the user to