Re: [v3 2/2] event: Correct dependencies on the EVENT framework

2023-01-20 Thread Simon Glass
Hi Tom, On Mon, 16 Jan 2023 at 14:04, Tom Rini wrote: > > On Mon, Jan 16, 2023 at 10:01:47PM +0100, Heinrich Schuchardt wrote: > > On 1/16/23 21:46, 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

Re: [v3 2/2] event: Correct dependencies on the EVENT framework

2023-01-19 Thread Tom Rini
On Mon, Jan 16, 2023 at 03:46:49PM -0500, 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_DYNAM

Re: [v3 2/2] event: Correct dependencies on the EVENT framework

2023-01-16 Thread Tom Rini
On Mon, Jan 16, 2023 at 10:01:47PM +0100, Heinrich Schuchardt wrote: > On 1/16/23 21:46, 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: [v3 2/2] event: Correct dependencies on the EVENT framework

2023-01-16 Thread Heinrich Schuchardt
On 1/16/23 21:46, 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

[v3 2/2] 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