mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: stefan.bader@canonical.com
Cc: linux-kernel@vger.kernel.org, gregkh@suse.de, stable@kernel.org,
	stable-commits@vger.kernel.org
Subject: Re: patch sparc64-make-prom-entry-spinlock-nmi-safe.patch added to 2.6.32-stable tree
Date: Tue, 30 Mar 2010 13:07:27 -0700 (PDT)	[thread overview]
Message-ID: <20100330.130727.119993073.davem@davemloft.net> (raw)
In-Reply-To: <4BB1E98E.9050702@canonical.com>

From: Stefan Bader <stefan.bader@canonical.com>
Date: Tue, 30 Mar 2010 14:07:42 +0200

> 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?

I don't think so.

      parent reply	other threads:[~2010-03-30 20:07 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <12689584863184@kroah.org>
2010-03-30 12:07 ` Stefan Bader
2010-03-30 20:05   ` [stable] " Greg KH
2010-03-31  7:18     ` Stefan Bader
2010-03-30 20:07   ` David Miller [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=20100330.130727.119993073.davem@davemloft.net \
    --to=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

Powered by JetHome