From: Sam Ravnborg <sam@ravnborg.org>
To: Mikael Pettersson <mikpe@it.uu.se>
Cc: Josip Rodin <joy@entuzijast.net>,
sparclinux@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH,SPARC] make sparc32 arch_write_unlock() match the sparc64 version
Date: Mon, 15 Aug 2011 17:24:36 +0200 [thread overview]
Message-ID: <20110815152436.GA31355@merkur.ravnborg.org> (raw)
In-Reply-To: <20041.11793.565236.115039@pilspetsen.it.uu.se>
Hi Mikael.
> > > @@ -175,7 +184,7 @@ static inline int __arch_read_trylock(ar
> > > res; \
> > > })
> > >
> > > -#define arch_write_unlock(rw) do { (rw)->lock = 0; } while(0)
> > > +#define arch_write_unlock(rw) arch_write_unlock(rw)
> > >
> > > #define arch_spin_lock_flags(lock, flags) arch_spin_lock(lock)
> > > #define arch_read_lock_flags(rw, flags) arch_read_lock(rw)
> >
> > Why keep the tautological define? Just wondering.
>
> Only because sparc64 does it that way. I now see that no other
> arch has the #define, so perhaps that bit should be deleted (from
> both sparc64 and sparc32).
Please kill the extra define in both sparc32 and sparc64.
Preferably in two separate patches.
For the subject of the patch please use:
[PATCH] sparc32: bla bla
Because when davem apply the patch everything in [] is zapped,
and it is good to see in the shortlog that this is a sparc32 specific patch.
For sparc64 we sometimes use "sparc64: bla bal", and sometimes use
"sparc: bla bla".
I prefer the first but no strong feelings.
And btw thanks for looking at this! Looks like a very difficult bug to nail.
Sam
prev parent reply other threads:[~2011-08-15 15:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-15 11:09 Mikael Pettersson
2011-08-15 13:31 ` Josip Rodin
2011-08-15 14:32 ` Mikael Pettersson
2011-08-15 15:24 ` Sam Ravnborg [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=20110815152436.GA31355@merkur.ravnborg.org \
--to=sam@ravnborg.org \
--cc=joy@entuzijast.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mikpe@it.uu.se \
--cc=sparclinux@vger.kernel.org \
/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
all inboxes | Powered by JetHome®