Received: by 2002:a25:e7d8:0:0:0:0:0 with SMTP id e207csp3547111ybh; Tue, 17 Mar 2020 02:06:06 -0700 (PDT) X-Google-Smtp-Source: ADFU+vuaEpAb8rmm+CDj0aHRffxIenIetdAj1NpIxuMg3tHIcBKrkucnqei2FA7BNCXQ7yuV67Ff X-Received: by 2002:a05:6830:4b1:: with SMTP id l17mr2811681otd.275.1584435966002; Tue, 17 Mar 2020 02:06:06 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1584435965; cv=none; d=google.com; s=arc-20160816; b=oXNZag1UUsNnn/wSm+Jo0xxuqthYm4VtkeW4R71O2RwYOKbBybO3YHZGFCjpf2Rjvj 9tNQmAqSxdyAUizVKQB64S4J36wc+mr6095+ti5kgjheyZJ4BrMt4bLiFtMsGonyg8sZ zQ9E2vQZVdPsfrfPRjDrWmAcZVIuRy2ZAVlwhg1VYZwiBVhLY++HO9cNNAQstc8oooJB nBAS2E9sQCijcNZWEp4nRIWG2b0XH17Tw9/nAhlsvMo7gOwlchf8pPECNHuY+mEGDiEb Ul4PU4Tfpej5OSgQmKAZvZqac3ernGVHKKoef6jGh39ctv7KBgKr/Xw/r2H2jxm6c6ir CViw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:mime-version:message-id:date:references :in-reply-to:subject:cc:to:from; bh=nblHSSH7f3+aUvKbdLg/IXAHJ+A1nvu/NYy1N0cjbl0=; b=Jay6ANSJNYWzlZH3tDv6BSt87N6iDQY8ZUnzl+vFmB0uSFc5CAm7fJcqYPS1DDJNT9 Zv3efC0K9ixobuQ+qSVccPN0Dofa3ubqck2zKjSUC4iQTII2enm9fhmrTffl3IU7odSR j9BPIy47nQ7WeIG4U/IymwlHlRvnyM7lEN4N+KcGJjWDixqoaMd+mzlECqZlC7DBM3l8 VWXiL1b3hAQ7D6yhe5m5DV11V9xOsOZ9f0+HT35JXEoNxwVBpwaLqj2y+eK816alQrcw VdAUn7dDgxdTCdrYoXHbvPDxMX/z+z8ocChRM8Be4Sw2EBVLe393xvsM/mvVFKPw8Al0 y6cQ== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id i132si921544oih.249.2020.03.17.02.05.53; Tue, 17 Mar 2020 02:06:05 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726077AbgCQJFL (ORCPT + 99 others); Tue, 17 Mar 2020 05:05:11 -0400 Received: from Galois.linutronix.de ([193.142.43.55]:53647 "EHLO Galois.linutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725872AbgCQJFL (ORCPT ); Tue, 17 Mar 2020 05:05:11 -0400 Received: from p5de0bf0b.dip0.t-ipconnect.de ([93.224.191.11] helo=nanos.tec.linutronix.de) by Galois.linutronix.de with esmtpsa (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1jE89p-0004bp-Tc; Tue, 17 Mar 2020 10:05:06 +0100 Received: by nanos.tec.linutronix.de (Postfix, from userid 1000) id BF3EF101161; Tue, 17 Mar 2020 10:05:04 +0100 (CET) From: Thomas Gleixner To: Logan Gunthorpe , linux-kernel@vger.kernel.org, linux-pci@vger.kernel.org, Bjorn Helgaas Cc: Sebastian Andrzej Siewior Subject: Re: [PATCH] PCI/switchtec: Fix init_completion race condition with poll_wait() In-Reply-To: <38781f88-32df-e89a-7d00-fd2fcc097497@deltatee.com> References: <20200313183608.2646-1-logang@deltatee.com> <87mu8fdck6.fsf@nanos.tec.linutronix.de> <38781f88-32df-e89a-7d00-fd2fcc097497@deltatee.com> Date: Tue, 17 Mar 2020 10:05:04 +0100 Message-ID: <87k13jcpxb.fsf@nanos.tec.linutronix.de> MIME-Version: 1.0 Content-Type: text/plain X-Linutronix-Spam-Score: -1.0 X-Linutronix-Spam-Level: - X-Linutronix-Spam-Status: No , -1.0 points, 5.0 required, ALL_TRUSTED=-1,SHORTCIRCUIT=-0.0001 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Logan Gunthorpe writes: > On 2020-03-16 6:56 p.m., Thomas Gleixner wrote: >> @Bjorn: Can you please hold off on this for a few days until we sorted >> out the remaining issues to avoid potential merge conflicts >> vs. the completion series? > > I'd suggest simply rebasing the completion patch on this patch, or a > patch like it. Then we'll have the proper bug fix commit and there won't > be a conflict. The conflict is not a question of rebasing or not. The conflict arises when this patch is routed through PCI simply because then the rest of the completion work is stuck until this hits mainline. Thanks, tglx