All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: Purcareata Bogdan <b43198@freescale.com>
Cc: linux-rt-users@vger.kernel.org, scottwood@freescale.com,
	Mihai Caraman <mihai.caraman@freescale.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] KVM: PPC: Convert openpic lock to raw_spinlock
Date: Wed, 18 Feb 2015 09:40:51 +0100	[thread overview]
Message-ID: <54E45013.4020005@linutronix.de> (raw)
In-Reply-To: <54E44DF8.1080906@freescale.com>

On 02/18/2015 09:31 AM, Purcareata Bogdan wrote:
> Thanks! Will send a patchset separating these 2 functional changes - the
> openpic raw_spinlock for upstream ppc (since it doesn't bring any
> changes anyway), and the MAX_VCPUS limitation for the RT tree.

thanks. please cc me on both.

>> This remains of my multiple-MSI patch which someone other posted a while
>> ago. What happend to it?
> 
> I'm not aware of this patch, could you give more details, please?

I just grabed them from archive and it seems that there were change
requests from Scott which were not done. Forget it then, I had it
differently in memory.

> 
> Bogdan P.

Sebastian

  reply	other threads:[~2015-02-18  8:40 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-22  9:39 [PATCH] KVM: PPC: Convert openpic lock to raw_spinlock Bogdan Purcareata
2015-02-02  9:35 ` Purcareata Bogdan
2015-02-17 12:27   ` Purcareata Bogdan
2015-02-17 17:53     ` Sebastian Andrzej Siewior
2015-02-17 17:59       ` Sebastian Andrzej Siewior
2015-02-18  8:31         ` Purcareata Bogdan
2015-02-18  8:40           ` Sebastian Andrzej Siewior [this message]
  -- strict thread matches above, loose matches on Subject: below --
2014-09-11 19:25 Bogdan Purcareata
2014-09-11 13:06 ` Bogdan Purcareata
2014-09-11 18:19 ` Scott Wood
2014-09-11 18:19   ` Scott Wood
2014-09-12 14:12   ` bogdan.purcareata
2014-09-12 14:12     ` bogdan.purcareata
2014-09-12 17:50     ` Scott Wood
2014-09-12 17:50       ` Scott Wood

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=54E45013.4020005@linutronix.de \
    --to=bigeasy@linutronix.de \
    --cc=b43198@freescale.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rt-users@vger.kernel.org \
    --cc=mihai.caraman@freescale.com \
    --cc=scottwood@freescale.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.