linux-modules.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Laura Abbott <labbott@redhat.com>
To: Lucas De Marchi <lucas.de.marchi@gmail.com>,
	Laura Abbott <labbott@fedoraproject.org>
Cc: Lucas De Marchi <lucas.demarchi@intel.com>,
	linux-modules <linux-modules@vger.kernel.org>
Subject: Re: [PATCH 3/4] depmod: Fix message printing before log_setup_kmod_log
Date: Fri, 18 Sep 2015 11:26:45 -0700	[thread overview]
Message-ID: <55FC5765.8020003@redhat.com> (raw)
In-Reply-To: <CAKi4VAKZRmiis6qD37OXZ5kxEXqy+rxVgYQrz=uVUSoY7ni_FQ@mail.gmail.com>

On 09/12/2015 11:55 AM, Lucas De Marchi wrote:
> On Fri, Sep 11, 2015 at 5:55 PM, Laura Abbott <labbott@fedoraproject.org> wrote:
>>
>> Until log_setup_kmod_log is called, the only messages that
>> can be printed are the default level. Bump a few deprecated
>> messages to ERR to ensure they get printed and drop some DBG
>> prints that will never occur unless the compiled default is DBG.
>> ---
>>   tools/depmod.c | 10 ++++------
>>   1 file changed, 4 insertions(+), 6 deletions(-)
>>
>> diff --git a/tools/depmod.c b/tools/depmod.c
>> index 2a08b6e..30f6191 100644
>> --- a/tools/depmod.c
>> +++ b/tools/depmod.c
>> @@ -2455,10 +2455,10 @@ static int do_depmod(int argc, char *argv[])
>>                  case 'r':
>>                  case 'm':
>>                          if (idx > 0)
>> -                               WRN("Ignored deprecated option --%s\n",
>> +                               ERR("Ignored deprecated option --%s\n",
>>                                      cmdopts[idx].name);
>>                          else
>> -                               WRN("Ignored deprecated option -%c\n", c);
>> +                               ERR("Ignored deprecated option -%c\n", c);
>
> /me confused. The default priority for depmod is LOG_WARNING
>

Right but it isn't set until you call log_setup_kmod_log. Until then it
uses the global default which is currently LOG_ERR so anything at a lower
level before this call is mostly useless. Changing the global default in
tools/log.c to LOG_WARN might be another option.

Thanks,
Laura

  reply	other threads:[~2015-09-18 18:26 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-11 20:55 [PATCH 0/4] depmod and modprobe error message fixups Laura Abbott
2015-09-11 20:55 ` [PATCH 1/4] build: Properly check for Cython Laura Abbott
2015-09-12 18:27   ` Lucas De Marchi
2015-09-18 17:38     ` Laura Abbott
2015-09-24  1:11       ` Lucas De Marchi
2015-09-11 20:55 ` [PATCH 2/4] modprobe: Add appropriate error message when path is missing Laura Abbott
2015-09-12 18:45   ` Lucas De Marchi
2015-09-11 20:55 ` [PATCH 3/4] depmod: Fix message printing before log_setup_kmod_log Laura Abbott
2015-09-12 18:55   ` Lucas De Marchi
2015-09-18 18:26     ` Laura Abbott [this message]
2015-09-24  1:16       ` Lucas De Marchi
2015-09-11 20:55 ` [PATCH 4/4] depmod: Add error message for bad version Laura Abbott
2015-09-12 19:00   ` Lucas De Marchi
2015-09-18 18:30     ` Laura Abbott
2015-09-24  1:17       ` Lucas De Marchi
2015-09-12 19:05 ` [PATCH 0/4] depmod and modprobe error message fixups Lucas De Marchi
2015-09-16 23:35   ` Kay Sievers

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=55FC5765.8020003@redhat.com \
    --to=labbott@redhat.com \
    --cc=labbott@fedoraproject.org \
    --cc=linux-modules@vger.kernel.org \
    --cc=lucas.de.marchi@gmail.com \
    --cc=lucas.demarchi@intel.com \
    /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;
as well as URLs for NNTP newsgroup(s).