[Re: [PATCH] mux-core: make it explicitly non-modular] On 09/03/2017 (Thu
13:01) Peter Rosin wrote:
> On 2017-03-09 10:39, Peter Rosin wrote:
>
> *snip* *snip*
>
> >> Per the above use case (minimal vmlinux) the unload isn't so important,
> >> and in many
[Re: [PATCH] mux-core: make it explicitly non-modular] On 09/03/2017 (Thu
13:01) Peter Rosin wrote:
> On 2017-03-09 10:39, Peter Rosin wrote:
>
> *snip* *snip*
>
> >> Per the above use case (minimal vmlinux) the unload isn't so important,
> >> and in many
On 2017-03-09 10:39, Peter Rosin wrote:
*snip* *snip*
>> Per the above use case (minimal vmlinux) the unload isn't so important,
>> and in many cases it may be racy or simply not make sense. If that is
>> the case, you don't need to provide a module_exit, and in the past I
>> think we used to
On 2017-03-09 10:39, Peter Rosin wrote:
*snip* *snip*
>> Per the above use case (minimal vmlinux) the unload isn't so important,
>> and in many cases it may be racy or simply not make sense. If that is
>> the case, you don't need to provide a module_exit, and in the past I
>> think we used to
On 2017-03-09 01:32, Paul Gortmaker wrote:
*snip* *snip*
> If the mux subsystem isn't board specific (and at a glance, it seems
> like it is not) then it might be the former and not the latter. But I
> leave that call up to you
The mux subsystem may be needed for some boards and not for others,
On 2017-03-09 01:32, Paul Gortmaker wrote:
*snip* *snip*
> If the mux subsystem isn't board specific (and at a glance, it seems
> like it is not) then it might be the former and not the latter. But I
> leave that call up to you
The mux subsystem may be needed for some boards and not for others,
[Re: [PATCH] mux-core: make it explicitly non-modular] On 08/03/2017 (Wed
16:32) Peter Rosin wrote:
> On 2017-03-08 15:38, Paul Gortmaker wrote:
[...]
> >
> > Note that mux-core doesn't have a .ko (modular variant) and also you can
> > confirm with nm that everything in m
[Re: [PATCH] mux-core: make it explicitly non-modular] On 08/03/2017 (Wed
16:32) Peter Rosin wrote:
> On 2017-03-08 15:38, Paul Gortmaker wrote:
[...]
> >
> > Note that mux-core doesn't have a .ko (modular variant) and also you can
> > confirm with nm that everything in m
On 2017-03-08 15:38, Paul Gortmaker wrote:
> [Re: [PATCH] mux-core: make it explicitly non-modular] On 08/03/2017 (Wed
> 10:38) Peter Rosin wrote:
>
>> On 2017-03-07 23:41, Paul Gortmaker wrote:
>>> The Kconfig currently controlling compilation of this code
On 2017-03-08 15:38, Paul Gortmaker wrote:
> [Re: [PATCH] mux-core: make it explicitly non-modular] On 08/03/2017 (Wed
> 10:38) Peter Rosin wrote:
>
>> On 2017-03-07 23:41, Paul Gortmaker wrote:
>>> The Kconfig currently controlling compilation of this code
[Re: [PATCH] mux-core: make it explicitly non-modular] On 08/03/2017 (Wed
10:38) Peter Rosin wrote:
> On 2017-03-07 23:41, Paul Gortmaker wrote:
> > The Kconfig currently controlling compilation of this code is:
> >
> > drivers/mux/Kconfig:menuconfig MULTIPLEXER
> > d
[Re: [PATCH] mux-core: make it explicitly non-modular] On 08/03/2017 (Wed
10:38) Peter Rosin wrote:
> On 2017-03-07 23:41, Paul Gortmaker wrote:
> > The Kconfig currently controlling compilation of this code is:
> >
> > drivers/mux/Kconfig:menuconfig MULTIPLEXER
> > d
On 2017-03-07 23:41, Paul Gortmaker wrote:
> The Kconfig currently controlling compilation of this code is:
>
> drivers/mux/Kconfig:menuconfig MULTIPLEXER
> drivers/mux/Kconfig:bool "Multiplexer subsystem"
>
> ...meaning that it currently is not being built as a module by anyone.
>
> Lets
On 2017-03-07 23:41, Paul Gortmaker wrote:
> The Kconfig currently controlling compilation of this code is:
>
> drivers/mux/Kconfig:menuconfig MULTIPLEXER
> drivers/mux/Kconfig:bool "Multiplexer subsystem"
>
> ...meaning that it currently is not being built as a module by anyone.
>
> Lets
The Kconfig currently controlling compilation of this code is:
drivers/mux/Kconfig:menuconfig MULTIPLEXER
drivers/mux/Kconfig:bool "Multiplexer subsystem"
...meaning that it currently is not being built as a module by anyone.
Lets remove the couple traces of modular infrastructure use, so
The Kconfig currently controlling compilation of this code is:
drivers/mux/Kconfig:menuconfig MULTIPLEXER
drivers/mux/Kconfig:bool "Multiplexer subsystem"
...meaning that it currently is not being built as a module by anyone.
Lets remove the couple traces of modular infrastructure use, so
16 matches
Mail list logo
