From: Samium Gromoff <deepfire@ibe.miee.ru>
To: linux-kernel@vger.kernel.org
Subject: Re: recursive spinlock. Shoot.
Date: Mon, 19 May 2003 13:59:48 +0400 [thread overview]
Message-ID: <20030519135948.0f0be20f.deepfire@ibe.miee.ru> (raw)
Not that my opinion matters much, but my feeling is that such measures
are very much of the bandaid taste, the ones which in the end piled one on another
end up obscuring the very problems in the code.
In short, it`ll probably make _filling_in_ the code easier, but the effect is
that it will shift the balance towards crap accumulation.
To me, that is the damage of the kind which is very hard to undo.
regards, Samium Gromoff
reply other threads:[~2003-05-19 10:45 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20030519135948.0f0be20f.deepfire@ibe.miee.ru \
--to=deepfire@ibe.miee.ru \
--cc=linux-kernel@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 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®