From: "David S. Miller" <davem@redhat.com>
To: neilb@cse.unsw.edu.au
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4.20-pre2 NFS OOPS on sparc64
Date: Tue, 13 Aug 2002 16:37:46 -0700 (PDT) [thread overview]
Message-ID: <20020813.163746.98327763.davem@redhat.com> (raw)
In-Reply-To: <15705.34786.933680.708535@notabene.cse.unsw.edu.au>
From: Neil Brown <neilb@cse.unsw.edu.au>
Date: Wed, 14 Aug 2002 08:27:46 +1000
Now if only Linus has told me (like you did) instead of just making
the change himself in 2.5, I would have got it right in 2.4..
Non-long pointers sent to bitops get a warning in 2.5.x so it just
automatically shows up in the build logs there.
prev parent reply other threads:[~2002-08-13 23:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-13 16:21 2.4.20-pre2 NFS OOPS on sparc64 Meelis Roos
2002-08-13 17:27 ` David S. Miller
2002-08-13 22:27 ` Neil Brown
2002-08-13 23:10 ` Alan Cox
2002-08-13 23:37 ` David S. Miller [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=20020813.163746.98327763.davem@redhat.com \
--to=davem@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=neilb@cse.unsw.edu.au \
/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