From: Ian Molton <spyro@f2s.com>
To: kernel-janitors@vger.kernel.org
Subject: [KJ] Re: [PATCH 0/2][RESEND] acorn: clean up printk()'s in
Date: Fri, 21 Jan 2005 16:40:53 +0000 [thread overview]
Message-ID: <41F13095.7010209@f2s.com> (raw)
In-Reply-To: <41F0F021.4050600@treblig.org>
Dave Gilbert (Home) wrote:
> James Nelson wrote:
>
>> This series of patches makes the printk()'s in drivers/acorn behave a
>> bit better.
>>
>> Re-sending them after noticing I used KERN_WARN instead of KERN_WARNING.
>>
>> Diffstat output:
>> fd1772.c | 142
>> +++++++++++++++++++++++++++++++--------------------------------
>> mfmhd.c | 138
>> ++++++++++++++++++++++++++++---------------------------------
>> 2 files changed, 136 insertions(+), 144 deletions(-)
>
>
> Those files are ancient - I haven't done anything on them in yonks; the
> right person to ask about this is Ian Molton - current maintainer of the
> ARM26/Archimedes world cc'd).
Hi there.
Im not sure whats best here. those files *are* ancient, and likely
differ somewhat from those in my current tree. I have done most of the
restructuring of arm26 now, but its still not quite actually *working*
yet. I have a whole diff full of driver updates and even some new
drivers, but Im reluctant to submit them at this point for a number of
reasons, not least of which is that they are often untested and some
conflict with mainstream arm.
I guess we could either:
leave them alone
update them
delete them pending me re-inserting working versions at some later date
other
_______________________________________________
Kernel-janitors mailing list
Kernel-janitors@lists.osdl.org
http://lists.osdl.org/mailman/listinfo/kernel-janitors
next prev parent reply other threads:[~2005-01-21 16:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-21 12:05 [KJ] Re: [PATCH 0/2][RESEND] acorn: clean up printk()'s in Dave Gilbert (Home)
2005-01-21 16:40 ` Ian Molton [this message]
2005-01-21 22:18 ` [KJ] Re: [PATCH 0/2][RESEND] acorn: clean up printk()'s Jim Nelson
2005-01-21 22:58 ` Ian Molton
2005-01-22 12:43 ` Dr. David Alan Gilbert
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=41F13095.7010209@f2s.com \
--to=spyro@f2s.com \
--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.