From: Rusty Russell <rusty@rustcorp.com.au>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: Dipankar Sarma <dipankar@gamebox.net>,
Petr Vandrovec <VANDROVE@vc.cvut.cz>,
linux-kernel@vger.kernel.org
Subject: Re: [TRIVIAL] Re: UP went into unexpected trashing
Date: Sun, 10 Nov 2002 14:09:22 +1100 [thread overview]
Message-ID: <20021110035807.9E0B22C28F@lists.samba.org> (raw)
In-Reply-To: Your message of "Fri, 08 Nov 2002 20:40:00 -0800." <Pine.LNX.4.44.0211082038580.1609-100000@home.transmeta.com>
In message <Pine.LNX.4.44.0211082038580.1609-100000@home.transmeta.com> you wri
te:
>
> On Sat, 9 Nov 2002, Rusty Russell wrote:
> > + * containing the bit) or a value >= size if none found.
>
> However, what was the original codepath that doesn't follow this and was
> the cause of the headache (ie the "unexpected trashing"?)
It was the "cpu masks become an unsigned long array" patch, which was
in Andrew Morton's mm tree, but you never took.
> Let's fix that user of the functions too, not just the documentation..
You're not adopting the Viro doctine are you? "On each new issue,
begin by assuming your peers are idiots". 8)
It's not becoming,
Rusty.
--
Anyone who quotes me in their sig is an idiot. -- Rusty Russell.
next prev parent reply other threads:[~2002-11-10 3:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-08 14:35 [TRIVIAL] Re: UP went into unexpected trashing Petr Vandrovec
2002-11-08 19:53 ` Dipankar Sarma
2002-11-08 20:10 ` Linus Torvalds
2002-11-09 3:16 ` Rusty Russell
2002-11-09 4:40 ` Linus Torvalds
2002-11-10 3:09 ` Rusty Russell [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-11-08 8:33 Rusty Trivial Russell
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=20021110035807.9E0B22C28F@lists.samba.org \
--to=rusty@rustcorp.com.au \
--cc=VANDROVE@vc.cvut.cz \
--cc=dipankar@gamebox.net \
--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 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.