From: Giacomo Catenazzi <cate@debian.org>
To: Dave Jones <davej@redhat.com>,
Ben Castricum <lk0806@bencastricum.nl>,
linux-kernel@vger.kernel.org, trivial@kernel.org,
Tigran Aivazian <tigran@aivazian.fsnet.co.uk>
Subject: Re: [patch] x86: microcode: Cosmetic changes
Date: Thu, 12 Jun 2008 07:52:42 +0200 [thread overview]
Message-ID: <4850B9AA.7030004@debian.org> (raw)
In-Reply-To: <20080611170939.GA15146@redhat.com>
Dave Jones wrote:
> On Tue, Jun 10, 2008 at 01:15:12PM +0200, Ben Castricum wrote:
> > @@ -805,6 +806,9 @@ static int __init microcode_init (void)
> > {
> > int error;
> >
> > + printk(KERN_INFO
> > + "IA-32 Microcode Update Driver: v" MICROCODE_VERSION " <tigran@aivazian.fsnet.co.uk>\n");
> > +
> > error = microcode_dev_init();
> > if (error)
> > return error;
> > @@ -825,9 +829,6 @@ static int __init microcode_init (void)
> > }
> >
> > register_hotcpu_notifier(&mc_cpu_notifier);
> > -
> > - printk(KERN_INFO
> > - "IA-32 Microcode Update Driver: v" MICROCODE_VERSION " <tigran@aivazian.fsnet.co.uk>\n");
> > return 0;
>
> By doing this before the registration of the sysdev, we'll
> now be printing this on machines that don't have the microcode
> update facility. Pointless spew, for no obvious gain imo.
>
> [Why we go through so many hoops before we check if the CPU is
> capable is a mystery to me. It would make more sense to have
> that be the first thing that gets checked when this inits]
I would remove the printk:
- it is the only email on my dmesg, along two other copyright
notices (Ingo and Intel). So it seems that the dmesg clean-up
is going on.
- the code of driver is stable, and now it is updated only in
kernel trees, so IMO it is better to use kernel version on
bug report. BTW I don't think people will update the version
number of driver.
- IMO it is enough to printk the microcode loads, not the
driver load.
ciao
cate
next prev parent reply other threads:[~2008-06-12 5:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-10 11:15 [patch] x86: microcode: Cosmetic changes Ben Castricum
2008-06-11 17:09 ` Dave Jones
2008-06-12 5:52 ` Giacomo Catenazzi [this message]
2008-06-12 7:48 ` Tigran Aivazian
2008-07-03 9:41 ` Ingo Molnar
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=4850B9AA.7030004@debian.org \
--to=cate@debian.org \
--cc=davej@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lk0806@bencastricum.nl \
--cc=tigran@aivazian.fsnet.co.uk \
--cc=trivial@kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.