From: "David S. Miller" <davem@redhat.com>
To: Chris Wright <chris@wirex.com>
Cc: Linus Torvalds <torvalds@transmeta.com>,
David Howells <dhowells@redhat.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] fix net/rxrpc/proc.c
Date: 12 May 2003 18:49:18 -0700 [thread overview]
Message-ID: <1052790558.9169.2.camel@rth.ninka.net> (raw)
In-Reply-To: <20030512173801.A20068@figure1.int.wirex.com>
On Mon, 2003-05-12 at 17:38, Chris Wright wrote:
> A recent change in 2.5.69-bk from Yoshfuji broke compilation of rxrpc
> code. It erroneously adds an owner field to the rxrpc_proc_peers_ops
> seq_operations. Fix below.
Why is it "erroneous"? Just add the proper linux/module.h include
to net/rxrpc/proc.c instead of spewing baseless claims.
--
David S. Miller <davem@redhat.com>
next prev parent reply other threads:[~2003-05-13 1:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-13 0:38 [PATCH] fix net/rxrpc/proc.c Chris Wright
2003-05-13 1:49 ` David S. Miller [this message]
2003-05-13 2:00 ` Chris Wright
2003-05-13 2:26 ` YOSHIFUJI Hideaki / 吉藤英明
2003-05-13 3:05 ` Chris Wright
2003-05-13 3:07 ` David S. Miller
2003-05-13 3:13 ` YOSHIFUJI Hideaki / 吉藤英明
2003-05-13 9:21 ` David Howells
2003-05-13 9:25 ` David Howells
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=1052790558.9169.2.camel@rth.ninka.net \
--to=davem@redhat.com \
--cc=chris@wirex.com \
--cc=dhowells@redhat.com \
--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