From: "David S. Miller" <davem@redhat.com>
To: szepe@pinerecords.com
Cc: marcelo@conectiva.com.br, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] warnkill trivia 2/2
Date: Sun, 01 Sep 2002 04:35:12 -0700 (PDT) [thread overview]
Message-ID: <20020901.043512.51698754.davem@redhat.com> (raw)
In-Reply-To: <20020901113741.GM32122@louise.pinerecords.com>
From: Tomas Szepe <szepe@pinerecords.com>
Date: Sun, 1 Sep 2002 13:37:42 +0200
> BTW who even passes around const atomic_t's? Ie. what
> genrated the warning and made you even edit this to begin with?
fs/reiserfs/buffer2.c, line ~28:
atomic_t gets the const quality on account of being a member
of a const struct buffer_head instance.
void wait_buffer_until_released (const struct buffer_head * bh)
{
Reiserfs is buggy, it means struct buffer_head const * bh
Let's keep the sparc atomic_read() how it is so more bugs
like this can be found.
next prev parent reply other threads:[~2002-09-01 11:37 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-01 10:56 [PATCH] warnkill trivia 2/2 Tomas Szepe
2002-09-01 10:57 ` David S. Miller
2002-09-01 11:28 ` Tomas Szepe
2002-09-01 11:25 ` David S. Miller
2002-09-01 11:37 ` Tomas Szepe
2002-09-01 11:35 ` David S. Miller [this message]
2002-09-01 12:10 ` Tomas Szepe
2002-09-01 12:16 ` David S. Miller
2002-09-01 12:39 ` Tomas Szepe
2002-09-01 21:57 ` Bruce Guenter
2002-09-02 22:24 ` Jan Hudec
2002-09-01 15:27 ` [PATCH] warnkill trivia 2/2 (correction) Tomas Szepe
-- strict thread matches above, loose matches on Subject: below --
2002-09-01 14:52 [PATCH] warnkill trivia 2/2 Mikael Pettersson
2002-09-01 14:56 ` Tomas Szepe
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=20020901.043512.51698754.davem@redhat.com \
--to=davem@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@conectiva.com.br \
--cc=szepe@pinerecords.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.