Received: by 2002:a25:683:0:0:0:0:0 with SMTP id 125csp1133372ybg; Thu, 4 Jun 2020 01:44:54 -0700 (PDT) X-Google-Smtp-Source: ABdhPJywqS0olyyXgDxZ3VPWJMecq9TDVwD5093vJQ+AZHCpNrikraOw+L4iEh42bkkVGrc+KSto X-Received: by 2002:a50:a981:: with SMTP id n1mr3084945edc.377.1591260294415; Thu, 04 Jun 2020 01:44:54 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1591260294; cv=none; d=google.com; s=arc-20160816; b=O/elpc4rMu+FJIUmYWz0NauykHjEOdWMFsViJE9uyOY8urOJae4g0iPqwep36dm06o ZSfGec2rr1sXK+50R8KCdA7eYN0BGhpED4hvijHzoV5mvB2wJzL/Y6Rib9NZqH8oP0kn sk8z2z22uHyKXqThW8/HmSEMLPgkosGtp+IuNYhSOOnjeTVx5qPaIixsdJ62Kg1S2t2S JSI0QKCMPmuYaIMR4BOn/Hdib7qmxKg2Mr55faijUNLodWR5PN4NRga78Z490galOJ1a wnUnbWhYLbEm/CyJuhSapYLGiexl8AHjc5UnNP1c/kN02CORt4CrNftXZyhhMVxf16op Lk4Q== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date; bh=wiSP8gPMx0V3beCvFvinpscV5CaZBYxj3SIHchMk7Hc=; b=d4mEc1FmKEfY5e74TfZ/SC6OFStjyLyveHzTGr8eyWWC5tDEzxbkn8rYDIvCBI06fr JN9FMW9aqFZgQ35YTUsvtdflDJzWixM5JOJNEAXIXC8mKaOybNmCU6tP5BuHo9uH4WDA yFAX4sClLOk7WhIdd37WV6aSsAXMpcINo93SfZ1TuDhJxNQYUBsP/H9c7Cgsw69WAADr 57lDk3ss5qGYEfpQJpTPzfH/C6UdJ2PNsvTapunPvI5yCFNYUVJqDuUoBlVd3SDCE0Xy NMiJgtvbzEc7TaqeapaPgTyLiQ2YjV3oF6tRLD990w7dgqVNT3SwxeSKems1Axzk/uXZ zcvQ== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id dv21si1299066ejb.220.2020.06.04.01.44.31; Thu, 04 Jun 2020 01:44:54 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728030AbgFDImJ (ORCPT + 99 others); Thu, 4 Jun 2020 04:42:09 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:56042 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726802AbgFDImJ (ORCPT ); Thu, 4 Jun 2020 04:42:09 -0400 Received: from Galois.linutronix.de (Galois.linutronix.de [IPv6:2a0a:51c0:0:12e:550::1]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 265C4C05BD1E; Thu, 4 Jun 2020 01:42:09 -0700 (PDT) Received: from [5.158.153.53] (helo=debian-buster-darwi.lab.linutronix.de) by Galois.linutronix.de with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.80) (envelope-from ) id 1jglRV-0008RC-Pp; Thu, 04 Jun 2020 10:41:41 +0200 Date: Thu, 4 Jun 2020 10:41:40 +0200 From: "Ahmed S. Darwish" To: Daniel Vetter Cc: Peter Zijlstra , Ingo Molnar , Will Deacon , Thomas Gleixner , "Paul E. McKenney" , "Sebastian A. Siewior" , Steven Rostedt , LKML , "David S. Miller" , Jakub Kicinski , Eric Dumazet , Jens Axboe , Vivek Goyal , linux-block@vger.kernel.org, David Airlie , Sumit Semwal , linux-media@vger.kernel.org, dri-devel@lists.freedesktop.org Subject: Re: [PATCH v2 0/6] seqlock: seqcount_t call sites bugfixes Message-ID: <20200604084139.GA1123871@debian-buster-darwi.lab.linutronix.de> References: <20200603144949.1122421-1-a.darwish@linutronix.de> <20200604072841.GR20149@phenom.ffwll.local> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20200604072841.GR20149@phenom.ffwll.local> User-Agent: Mutt/1.10.1 (2018-07-13) 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 On Thu, Jun 04, 2020 at 09:28:41AM +0200, Daniel Vetter wrote: > On Wed, Jun 03, 2020 at 04:49:43PM +0200, Ahmed S. Darwish wrote: > > Hi, > > > > Since patch #7 and #8 from the series: > > > > [PATCH v1 00/25] seqlock: Extend seqcount API with associated locks > > https://lore.kernel.org/lkml/20200519214547.352050-1-a.darwish@linutronix.de > > > > are now pending on the lockdep/x86 IRQ state tracking patch series: > > > > [PATCH 00/14] x86/entry: disallow #DB more and x86/entry lockdep/nmi > > https://lkml.kernel.org/r/20200529212728.795169701@infradead.org > > > > [PATCH v3 0/5] lockdep: Change IRQ state tracking to use per-cpu variables > > https://lkml.kernel.org/r/20200529213550.683440625@infradead.org > > > > This is a repost only of the seqcount_t call sites bugfixes that were on > > top of the seqlock patch series. > > > > These fixes are independent, and can thus be merged on their own. I'm > > reposting them now so they can at least hit -rc2 or -rc3. > > I'm confused on what I should do with patch 6 here for dma-buf. Looks like > just a good cleanup/prep work, so I'd queue it for linux-next and 5.9, but > sounds like you want this in earlier. Do you need this in 5.8-rc for some > work meant for 5.9? Will this go in through some topic branch directly? > Should I apply it? > > Patch itself lgtm, I'm just confused what I should do with it. > My apologies for the confusion. The cover letter is indeed misleading w.r.t. the dma-buf patch. It isn't a bugfix, so it shouldn't hit -rc. Since without this patch compiling the seqcount series will fail, it will be best to merge it through tip instead. So all I need for now is a reviewed-by tag :) I will forwoard it to the tip tree afterwards. Thanks, -- Ahmed S. Darwish Linutronix GmbH