From: Richard Gooch <rgooch@ras.ucalgary.ca>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: vda@port.imtp.ilyichevsk.odessa.ua,
tao@acc.umu.se (David Weinehall),
brand@jupiter.cs.uni-dortmund.de (Horst von Brand),
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] KERN_INFO for devfs
Date: Wed, 30 Jan 2002 11:04:49 -0700 [thread overview]
Message-ID: <200201301804.g0UI4nQ13064@vindaloo.ras.ucalgary.ca> (raw)
In-Reply-To: <E16VwTl-0007VJ-00@the-village.bc.nu>
In-Reply-To: <200201301232.g0UCWmt10496@Port.imtp.ilyichevsk.odessa.ua> <E16VwTl-0007VJ-00@the-village.bc.nu>
Alan Cox writes:
> > > Yes, but that may change (in theory, at least.) Consistency is a virtue.
> >
> > I'll do this cleanup if my KERN_INFO patches will be accepted, at least some
> > of them. So far only Richard Gooch replied...
>
> I ran some of them into 7ac1 but got rejects so I've dumped them out
> for now. They mostly look completely sensible
I'd prefer if tree maintainers (that means you, Alan:-) don't apply
devfs patches that didn't come from me. I've already posted a patch
which cleans up *all* the remaining printk()'s. In fact, it's a pair
of patches, one for 2.4.x and one for 2.5.x. That was yesterday. Today
I'm still seeing this thread being beaten to death.
Besides, this is hardly an urgent fix, so there's no great rush to
apply a random patch from someone else, even if I did sit on it for a
week or two. Applying random patches will just end up generating more
merge work for me down the track.
Regards,
Richard....
Permanent: rgooch@atnf.csiro.au
Current: rgooch@ras.ucalgary.ca
next prev parent reply other threads:[~2002-01-30 18:07 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-28 11:50 Denis Vlasenko
2002-01-28 16:44 ` Richard Gooch
2002-01-29 1:20 ` Denis Vlasenko
2002-01-29 16:49 ` Horst von Brand
2002-01-30 13:03 ` Denis Vlasenko
2002-01-30 11:09 ` David Weinehall
2002-01-30 16:32 ` Denis Vlasenko
2002-01-30 12:34 ` Zwane Mwaikambo
2002-01-30 15:16 ` Alan Cox
2002-01-30 18:04 ` Richard Gooch [this message]
2002-01-30 18:20 ` Richard Gooch
2002-01-30 18:32 ` Alan Cox
2002-01-30 19:37 ` Jeff Garzik
2002-01-31 20:44 ` Horst von Brand
2002-01-29 7:27 Borsenkow Andrej
2002-01-29 13:40 ` Denis Vlasenko
2002-01-29 10:39 ` Borsenkow Andrej
2002-01-29 15:40 ` Denis Vlasenko
2002-01-29 17:48 ` Richard Gooch
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=200201301804.g0UI4nQ13064@vindaloo.ras.ucalgary.ca \
--to=rgooch@ras.ucalgary.ca \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=brand@jupiter.cs.uni-dortmund.de \
--cc=linux-kernel@vger.kernel.org \
--cc=tao@acc.umu.se \
--cc=vda@port.imtp.ilyichevsk.odessa.ua \
/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
all inboxes | Powered by JetHome®