Sorry I didn't see this mail until now - RE:
Randy Dunlap wrote:
> Would someone please answer/reply to this (related) kernel bugzilla entry:
> https://bugzilla.kernel.org/show_bug.cgi?id=118661
Yes, I raised this bug because I think modinfo should return 0 exit status
if
Sorry I didn't see this mail until now - RE:
Randy Dunlap wrote:
> Would someone please answer/reply to this (related) kernel bugzilla entry:
> https://bugzilla.kernel.org/show_bug.cgi?id=118661
Yes, I raised this bug because I think modinfo should return 0 exit status
if a requested module is
On 02/24/2015 05:02 PM, Lucas De Marchi wrote:
> On Mon, Feb 23, 2015 at 12:51 PM, Michal Marek wrote:
>> On 2015-02-23 15:30, Lucas De Marchi wrote:
>>> This could be particularly bad if in a kernel version an option was
>>> tristate and in a new version it changed to boolean.
On 02/24/2015 05:02 PM, Lucas De Marchi wrote:
> On Mon, Feb 23, 2015 at 12:51 PM, Michal Marek wrote:
>> On 2015-02-23 15:30, Lucas De Marchi wrote:
>>> This could be particularly bad if in a kernel version an option was
>>> tristate and in a new version it changed to boolean. I'm not sure if
On Wed, Feb 25, 2015 at 8:53 AM, Michal Marek wrote:
> On Tue, Feb 24, 2015 at 10:02:55PM -0300, Lucas De Marchi wrote:
>> On Mon, Feb 23, 2015 at 12:51 PM, Michal Marek wrote:
>> > On 2015-02-23 15:30, Lucas De Marchi wrote:
>> >> My questions are:
>> >> 1) should we put *all* the "modules" in
On Wed, Feb 25, 2015 at 8:53 AM, Michal Marek mma...@suse.cz wrote:
On Tue, Feb 24, 2015 at 10:02:55PM -0300, Lucas De Marchi wrote:
On Mon, Feb 23, 2015 at 12:51 PM, Michal Marek mma...@suse.cz wrote:
On 2015-02-23 15:30, Lucas De Marchi wrote:
My questions are:
1) should we put *all* the
On Tue, Feb 24, 2015 at 10:02:55PM -0300, Lucas De Marchi wrote:
> On Mon, Feb 23, 2015 at 12:51 PM, Michal Marek wrote:
> > On 2015-02-23 15:30, Lucas De Marchi wrote:
> >> My questions are:
> >> 1) should we put *all* the "modules" in the builtin index?
> >
> > You mean all *.o files that do
On Tue, Feb 24, 2015 at 10:02:55PM -0300, Lucas De Marchi wrote:
On Mon, Feb 23, 2015 at 12:51 PM, Michal Marek mma...@suse.cz wrote:
On 2015-02-23 15:30, Lucas De Marchi wrote:
My questions are:
1) should we put *all* the modules in the builtin index?
You mean all *.o files that do not
On Tue, Feb 24, 2015 at 8:42 AM, Harish Jenny Kandiga Nagaraj
wrote:
>
> On Monday 23 February 2015 09:21 PM, Michal Marek wrote:
>> On 2015-02-23 15:30, Lucas De Marchi wrote:
> Can we add some flag like
> KMOD_PROBE_FORCE_DIRECTORY_CHECK = 0x00040,
> and pass it to kmod_module_get_initstate to
On Mon, Feb 23, 2015 at 12:51 PM, Michal Marek wrote:
> On 2015-02-23 15:30, Lucas De Marchi wrote:
>> This could be particularly bad if in a kernel version an option was
>> tristate and in a new version it changed to boolean. I'm not sure if
>> this is common to happen in kernel. Any code that
On Monday 23 February 2015 09:21 PM, Michal Marek wrote:
> On 2015-02-23 15:30, Lucas De Marchi wrote:
>> This could be particularly bad if in a kernel version an option was
>> tristate and in a new version it changed to boolean. I'm not sure if
>> this is common to happen in kernel. Any code
On Monday 23 February 2015 09:21 PM, Michal Marek wrote:
On 2015-02-23 15:30, Lucas De Marchi wrote:
This could be particularly bad if in a kernel version an option was
tristate and in a new version it changed to boolean. I'm not sure if
this is common to happen in kernel. Any code that did
On Mon, Feb 23, 2015 at 12:51 PM, Michal Marek mma...@suse.cz wrote:
On 2015-02-23 15:30, Lucas De Marchi wrote:
This could be particularly bad if in a kernel version an option was
tristate and in a new version it changed to boolean. I'm not sure if
this is common to happen in kernel. Any code
On Tue, Feb 24, 2015 at 8:42 AM, Harish Jenny Kandiga Nagaraj
harish_kand...@mentor.com wrote:
On Monday 23 February 2015 09:21 PM, Michal Marek wrote:
On 2015-02-23 15:30, Lucas De Marchi wrote:
Can we add some flag like
KMOD_PROBE_FORCE_DIRECTORY_CHECK = 0x00040,
and pass it to
On 2015-02-23 15:30, Lucas De Marchi wrote:
> This could be particularly bad if in a kernel version an option was
> tristate and in a new version it changed to boolean. I'm not sure if
> this is common to happen in kernel. Any code that did "modprobe
> " would start to fail.
I think it's quite
Changing the subject because this is unrelated to the patch to kmod. It was:
[PATCH] libkmod-module: Remove directory existence check for KMOD_MODULE_BUILTIN
CC'ing Michael Marek who created the modules.builtin file a while ago.
On Thu, Feb 19, 2015 at 12:25 AM, Rusty Russell wrote:
>> Rusty,
Changing the subject because this is unrelated to the patch to kmod. It was:
[PATCH] libkmod-module: Remove directory existence check for KMOD_MODULE_BUILTIN
CC'ing Michael Marek who created the modules.builtin file a while ago.
On Thu, Feb 19, 2015 at 12:25 AM, Rusty Russell
On 2015-02-23 15:30, Lucas De Marchi wrote:
This could be particularly bad if in a kernel version an option was
tristate and in a new version it changed to boolean. I'm not sure if
this is common to happen in kernel. Any code that did modprobe
module would start to fail.
I think it's quite
18 matches
Mail list logo