From: Miles Bader <miles@lsi.nec.co.jp>
To: Andrey Panin <pazke@donpac.ru>
Cc: Anton Blanchard <anton@samba.org>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH][RFC] irq handling code consolidation (common part)
Date: 27 Jun 2003 15:04:13 +0900 [thread overview]
Message-ID: <buowuf86opu.fsf@mcspd15.ucom.lsi.nec.co.jp> (raw)
In-Reply-To: <20030627050020.GX9679@pazke>
Andrey Panin <pazke@donpac.ru> writes:
> BTW sparc implementation of irq_itoa() uses static buffer for the formatted
> string, is it really irq/preempt safe ?
Passinf in a result buffer seems simplest (maybe have the arch define a
macro for the max-length).
[btw the name `irq_itoa' seems a bit odd; how about `irq_name' (or
`irq_rep' for clu-lovers)?]
-miLes
--
Somebody has to do something, and it's just incredibly pathetic that it
has to be us. -- Jerry Garcia
prev parent reply other threads:[~2003-06-27 5:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-26 11:02 Andrey Panin
2003-06-26 11:13 ` Christoph Hellwig
2003-06-27 4:33 ` Andrey Panin
2003-06-26 17:55 ` Anton Blanchard
2003-06-27 5:00 ` Andrey Panin
2003-06-27 6:04 ` Miles Bader [this message]
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=buowuf86opu.fsf@mcspd15.ucom.lsi.nec.co.jp \
--to=miles@lsi.nec.co.jp \
--cc=anton@samba.org \
--cc=linux-kernel@vger.kernel.org \
--cc=miles@gnu.org \
--cc=pazke@donpac.ru \
/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®