From: Andreas Schwab <schwab@suse.de>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] Idenitfier clash in read_[un]lock
Date: Wed, 19 Mar 2003 09:53:30 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590723705270@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590709806152@msgid-missing>
David Mosberger <davidm@napali.hpl.hp.com> writes:
|> >>>>> On Tue, 18 Mar 2003 15:33:42 +0100, Andreas Schwab <schwab@suse.de> said:
|>
|> Andreas> The read_lock and read_unlock macros should not use such
|> Andreas> innocent variable names like tmp because they have a high
|> Andreas> probability to clash with (part of) the argument.
|>
|> Thanks, I applied this patch for 2.5. In the future, it would be nice
|> if you could send patches that apply with "patch -p1" and if you could
|> specify what kernel the patch is relative to.
Sorry, I'll take more care the next time.
Thanks, Andreas.
--
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux AG, Deutschherrnstr. 15-19, D-90429 Nürnberg
Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
prev parent reply other threads:[~2003-03-19 9:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-18 14:33 [Linux-ia64] Idenitfier clash in read_[un]lock Andreas Schwab
2003-03-18 23:00 ` David Mosberger
2003-03-19 9:53 ` Andreas Schwab [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=marc-linux-ia64-105590723705270@msgid-missing \
--to=schwab@suse.de \
--cc=linux-ia64@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