netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Or Gerlitz <or.gerlitz@gmail.com>
Cc: Or Gerlitz <ogerlitz@mellanox.com>, Tejun Heo <tj@kernel.org>,
	Ming Lei <ming.lei@canonical.com>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	David Miller <davem@davemloft.net>,
	Roland Dreier <roland@kernel.org>,
	netdev <netdev@vger.kernel.org>, Yan Burman <yanb@mellanox.com>,
	Jack Morgenstein <jackm@dev.mellanox.co.il>,
	Bjorn Helgaas <bhelgaas@google.com>,
	linux-pci@vger.kernel.org
Subject: Re: [PATCH repost for-3.9] pci: avoid work_on_cpu for nested SRIOV probes
Date: Thu, 18 Apr 2013 23:03:06 +0300	[thread overview]
Message-ID: <20130418200306.GA22435@redhat.com> (raw)
In-Reply-To: <CAJZOPZLuT7jcUJi_EEQ1_fgVCuFHk1Xzbb6kQtPSS4LfL=ArVg@mail.gmail.com>

On Thu, Apr 18, 2013 at 09:41:31PM +0300, Or Gerlitz wrote:
> On Thu, Apr 18, 2013 at 4:54 PM, Michael S. Tsirkin <mst@redhat.com> wrote:
> [...]
> > Tejun, what do you say my patch is used for 3.9, and we can revisit for 3.10.
> > The release is almost here. If yes please send your Ack.
> 
> Michael,
> 
> I assume you mean pull to 3.9 both Tejun's and your patch, correct? I
> wasn't sure what does this really buys us... we got read from the
> false-positive lockdep warning which takes place during nested probe
> and got another lockdep warning during the probe of Interrupt
> controller
> 
> Or.

No I mean my original patch.

      reply	other threads:[~2013-04-18 20:03 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-11 15:30 [PATCH repost for-3.9] pci: avoid work_on_cpu for nested SRIOV probes Michael S. Tsirkin
2013-04-11 18:05 ` Tejun Heo
2013-04-11 18:58   ` Michael S. Tsirkin
2013-04-11 19:04     ` Tejun Heo
2013-04-11 19:17       ` Michael S. Tsirkin
2013-04-11 19:20         ` Tejun Heo
2013-04-11 20:30           ` Michael S. Tsirkin
2013-04-11 20:41             ` Tejun Heo
2013-04-11 21:52               ` Or Gerlitz
2013-04-14 12:58               ` Or Gerlitz
2013-04-14 13:43                 ` Tejun Heo
2013-04-18  8:33                   ` Michael S. Tsirkin
2013-04-18  9:40                     ` Jack Morgenstein
2013-04-18  8:48                       ` Michael S. Tsirkin
2013-04-18  9:57                         ` Jack Morgenstein
2013-04-18 14:49                     ` Or Gerlitz
2013-04-18 13:54                       ` Michael S. Tsirkin
2013-04-18 18:19                         ` Tejun Heo
2013-04-18 18:25                           ` Bjorn Helgaas
2013-04-18 20:11                             ` Michael S. Tsirkin
2013-04-18 18:41                         ` Or Gerlitz
2013-04-18 20:03                           ` Michael S. Tsirkin [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=20130418200306.GA22435@redhat.com \
    --to=mst@redhat.com \
    --cc=bhelgaas@google.com \
    --cc=davem@davemloft.net \
    --cc=gregkh@linuxfoundation.org \
    --cc=jackm@dev.mellanox.co.il \
    --cc=linux-pci@vger.kernel.org \
    --cc=ming.lei@canonical.com \
    --cc=netdev@vger.kernel.org \
    --cc=ogerlitz@mellanox.com \
    --cc=or.gerlitz@gmail.com \
    --cc=roland@kernel.org \
    --cc=tj@kernel.org \
    --cc=yanb@mellanox.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;
as well as URLs for NNTP newsgroup(s).