From: David Miller <davem@davemloft.net>
To: torvalds@linux-foundation.org
Cc: arnd@arndb.de, fweisbec@gmail.com, tglx@linutronix.de,
jkacur@redhat.com, sam@ravnborg.org, jblunck@suse.de,
linux-kernel@vger.kernel.org
Subject: Re: [RFC] annotating the remaining BKL users
Date: Wed, 08 Sep 2010 20:53:20 -0700 (PDT) [thread overview]
Message-ID: <20100908.205320.191416862.davem@davemloft.net> (raw)
In-Reply-To: <AANLkTikfLb+kDZN8aodPwxFuL_VOuyb7AH=eF60MwrWG@mail.gmail.com>
From: Linus Torvalds <torvalds@linux-foundation.org>
Date: Wed, 8 Sep 2010 17:20:57 -0700
> That said, I'd also like to see a comment _why_ the architectures in
> question depends on the BKL. Some of those look pretty historical (the
> sparc32 register window spill code? Does it _really_ need the BKL at
> all, or is that just a remnant of "let's get the BKL at each kernel
> entry").
It probably doesn't or can be trivially removed.
I'll have a go at this.
next prev parent reply other threads:[~2010-09-09 3:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-08 20:55 Arnd Bergmann
2010-09-09 0:20 ` Linus Torvalds
2010-09-09 3:53 ` David Miller [this message]
2010-09-09 11:15 ` Arnd Bergmann
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=20100908.205320.191416862.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=arnd@arndb.de \
--cc=fweisbec@gmail.com \
--cc=jblunck@suse.de \
--cc=jkacur@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sam@ravnborg.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.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®