From: Greg KH <greg@kroah.com>
To: Stefan Bader <stefan.bader@canonical.com>
Cc: linux-kernel@vger.kernel.org, stable-commits@vger.kernel.org,
gregkh@suse.de, davem@davemloft.net, stable@kernel.org
Subject: Re: [stable] patch sparc64-make-prom-entry-spinlock-nmi-safe.patch added to 2.6.32-stable tree
Date: Tue, 30 Mar 2010 13:05:22 -0700 [thread overview]
Message-ID: <20100330200522.GD1693@kroah.com> (raw)
In-Reply-To: <4BB1E98E.9050702@canonical.com>
On Tue, Mar 30, 2010 at 02:07:42PM +0200, Stefan Bader wrote:
> This converted the raw_spinlock usage which is used in the upstream patch but
> not available in 2.6.32 to normal spinlock usage. Should it get annotated to
> document that?
why, you obviously figured that out :)
It's not the normal thing to do for backports otherwise we would be here
all day long...
thanks,
greg k-h
next prev parent reply other threads:[~2010-03-30 20:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <12689584863184@kroah.org>
2010-03-30 12:07 ` patch sparc64-make-prom-entry-spinlock-nmi-safe.patch added to 2.6.32-stable tree Stefan Bader
2010-03-30 20:05 ` Greg KH [this message]
2010-03-31 7:18 ` [stable] " Stefan Bader
2010-03-30 20:07 ` David Miller
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=20100330200522.GD1693@kroah.com \
--to=greg@kroah.com \
--cc=davem@davemloft.net \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=stable-commits@vger.kernel.org \
--cc=stable@kernel.org \
--cc=stefan.bader@canonical.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox