From: Remco Post <r.post@sara.nl>
To: <linux-kernel@vger.kernel.org>, Linus Torvalds <torvalds@transmeta.com>
Subject: [TRIVIAL PATCH] typo in svclock.c (linuxppc-2.5 tree)
Date: Tue, 10 Sep 2002 23:33:49 +0200 [thread overview]
Message-ID: <20020910233349.613c01ae.r.post@sara.nl> (raw)
Hi,
did a rr in vi and then some diff -c:
*** linuxppc-2.5/fs/lockd/svclock.c.org Tue Sep 10 23:13:29 2002
--- linuxppc-2.5/fs/lockd/svclock.c Tue Sep 10 23:16:37 2002
***************
*** 467,473 ****
* the block to the head of nlm_blocked where it can be picked up by lockd.
*/
static void
! nlmsvc_notify_blocked(stsuct file_lock *fl)
{
struct nlm_block **bp, *block;
--- 467,473 ----
* the block to the head of nlm_blocked where it can be picked up by lockd.
*/
static void
! nlmsvc_notify_blocked(struct file_lock *fl)
{
struct nlm_block **bp, *block;
reply other threads:[~2002-09-10 21:29 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=20020910233349.613c01ae.r.post@sara.nl \
--to=r.post@sara.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
/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®