All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kevin Brosius <cobra@compuserve.com>
To: kernel <linux-kernel@vger.kernel.org>, netdev@oss.sgi.com
Cc: Joe@perches.com
Subject: Re: [PATCH] 2.6.0-test4 SEQ_START_TOKEN net/* (2/6)
Date: Tue, 09 Sep 2003 22:11:22 -0400	[thread overview]
Message-ID: <3F5E884A.E62D27EE@compuserve.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 152 bytes --]

This patch to net/appletalk/aarp.c seemed fine, however it seems it
changed prior to hitting the bk tree.  The attached is needed to
compile.

-- 
Kevin

[-- Attachment #2: patch_aarp_bk.diff --]
[-- Type: text/plain, Size: 924 bytes --]

# This is a BitKeeper generated patch for the following project:
# Project Name: Linux kernel tree
# This patch format is intended for GNU patch command version 2.5 or higher.
# This patch includes the following deltas:
#	           ChangeSet	1.1238  -> 1.1239 
#	net/appletalk/aarp.c	1.17    -> 1.18   
#
# The following is the BitKeeper ChangeSet Log
# --------------------------------------------
# 03/09/09	cobra@sea.kevb.net	1.1239
# Fixup typo
# --------------------------------------------
#
diff -Nru a/net/appletalk/aarp.c b/net/appletalk/aarp.c
--- a/net/appletalk/aarp.c	Tue Sep  9 22:05:25 2003
+++ b/net/appletalk/aarp.c	Tue Sep  9 22:05:25 2003
@@ -941,7 +941,7 @@
 	iter->table     = resolved;
 	iter->bucket    = 0;
 
-	return *pos ? iter_next(iter, pos) : SEQ_START_TOKEN);
+	return *pos ? iter_next(iter, pos) : SEQ_START_TOKEN;
 }
 
 static void *aarp_seq_next(struct seq_file *seq, void *v, loff_t *pos)

             reply	other threads:[~2003-09-10  2:13 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-10  2:11 Kevin Brosius [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-09-06  1:47 [PATCH] 2.6.0-test4 SEQ_START_TOKEN net/* (2/6) Joe Perches

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=3F5E884A.E62D27EE@compuserve.com \
    --to=cobra@compuserve.com \
    --cc=Joe@perches.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@oss.sgi.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.