All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@suse.de>
To: kernel-janitors@vger.kernel.org
Subject: [KJ] Re: [PATCH] usb.h: reduce syslog clutter
Date: Mon, 20 Mar 2006 20:39:51 +0000	[thread overview]
Message-ID: <20060320203951.GA19025@suse.de> (raw)
In-Reply-To: <20060320194109.GA16890@suse.de>

[-- Attachment #1: Type: text/plain, Size: 1699 bytes --]

On Mon, Mar 20, 2006 at 09:00:11PM +0100, Tilman Schmidt wrote:
> On 20.03.2006 20:41, Greg KH wrote:
> 
> > On Sat, Mar 18, 2006 at 08:53:26PM +0100, Tilman Schmidt wrote:
> > 
> >>The current versions of the err() / info() / warn() message macros in
> >>include/linux/usb.h insert __FILE__ at the beginning of the message.
> >>[...]
> >>The following patch modifies these macros so that, when used in a
> >>module, they'll insert the module name instead, which is significantly
> >>shorter and also tends to be more useful to users (as opposed to kernel
> >>developers) trying to make sense of a particular message.
> >>
> >>It also adds a macro for the "notice" message level which was missing
> >>so far.
> >[...]
> > What was wrong with my suggestion that we simply delete these macros and
> > convert the USB code over to using the proper dev_info(), dev_warn(),
> > dev_err(), and dev_notice() macros instead?
> 
> Just that, as you remarked yourself:
> 
> > [T]here are a few places in the USB code that do
> > not have a valid device and so they can't be dropped entirely.
> 
> and I still don't see how to handle that situation with the dev_ macros.
> 
> But I thought you said you would accept that patch if I submitted it
> through the kernel-janitors. Why the change of mind?

No, I think you misunderstood me.  I said that converting the USB code
over to using the proper dev_* macros would be a good janitor's project,
not that you need to submit this patch through them.

There are only a very few places that these macros can not be used, and
only after converting everything that can possibly be changed, then we
can see if these are still really needed or not.

thanks,

greg k-h

[-- Attachment #2: Type: text/plain, Size: 168 bytes --]

_______________________________________________
Kernel-janitors mailing list
Kernel-janitors@lists.osdl.org
https://lists.osdl.org/mailman/listinfo/kernel-janitors

  parent reply	other threads:[~2006-03-20 20:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-20 19:41 [KJ] Re: [PATCH] usb.h: reduce syslog clutter Greg KH
2006-03-20 20:00 ` Tilman Schmidt
2006-03-20 20:39 ` Greg KH [this message]
2006-03-21  0:56 ` Tilman Schmidt
2006-03-22 20:56 ` Greg KH

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=20060320203951.GA19025@suse.de \
    --to=gregkh@suse.de \
    --cc=kernel-janitors@vger.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.