From: "David C. Hansen" <haveblue@us.ibm.com>
To: Alex Valys <avalys@optonline.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: PATCH: Spinlock Macro Arguments Correction in pc_keyb.c
Date: Thu, 29 Nov 2001 16:43:09 -0800 [thread overview]
Message-ID: <3C06D61D.2000803@us.ibm.com> (raw)
In-Reply-To: <0GNL00C2J5G9JN@mta6.srv.hcvlny.cv.net>
Alex Valys wrote:
>Not having ever done any serious kernel programming, I have only a dim
>understanding of what spinlocks are, but by looking at those macro
>definitions in spinlock.h (and their occurences elsewhere in the file) I
>think I determined their proper usage. The following patch fixed the compile
>errors, and I'm using 2.5.1-pre3 to type this message.
>
>This is my first patch, so if I did anything wrong please correct me.
>-Alex Valys
>
That looks like an error as a result of one of my patches. Your
solution looks correct. Make sure to send it over to Linus. Nice job
with your first patch!
David C. Hansen
haveblue@us.ibm.com
prev parent reply other threads:[~2001-11-30 0:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-29 23:33 PATCH: Spinlock Macro Arguments Correction in pc_keyb.c Alex Valys
2001-11-30 0:43 ` David C. Hansen [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=3C06D61D.2000803@us.ibm.com \
--to=haveblue@us.ibm.com \
--cc=avalys@optonline.net \
--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;
as well as URLs for NNTP newsgroup(s).