Received: by 2002:a25:6193:0:0:0:0:0 with SMTP id v141csp2154668ybb; Sat, 4 Apr 2020 23:57:59 -0700 (PDT) X-Google-Smtp-Source: APiQypI5ZQ7lGO3cYE4khIZZIhmfglSQppTgvFi6jTJDGN8ENgVGSBf5oCj8LC5mxdtlTFFmC0c+ X-Received: by 2002:a05:6830:1e10:: with SMTP id s16mr13242758otr.33.1586069879273; Sat, 04 Apr 2020 23:57:59 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1586069879; cv=none; d=google.com; s=arc-20160816; b=pMSL3b5wfuMjwL4Zd0chklqF8RZ9mHuBC7FXrV0Ir33Gf1RLdHrmOhZXtlAgk2nPD2 B6JkWGmu8LvIpsjy+CNwIEcw7wuP2UG7dT137OyVoO3E8lOTSw0hMho8Y90Lx/cNxCKx tFM0gFK7VZx2kRvSwANKitFuWTIRhq9rRVqKFmxHiuoIF7ClbUZLB2f14XWlZd5Kj42V IzFmD/OswtsxXFjV2W3GPixDg8GKKC0J1D4a/0/lufNDWVj7i74BwgnU7iUE23aSs2UF UkqAy2/27ahqtZ0zPpt+II8Y/Vadk+7b+W6almpKBVqcUDXtNOyCPmB1eJnJT3nJiQv+ F0TA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:subject:cc:to:from:date:references :in-reply-to:message-id:mime-version:user-agent:dkim-signature :dkim-signature; bh=A9dbn5+Kyg5hHH3Cxnfh6Nqgtjiyajyp0XRJXLne8is=; b=qW5Rr7Hk1+4rrG20i35jnRYkIe97xY0+P2EucVGMmagTqxw2KFDFbibzMyC1A8TXx+ attwsbqj1XcA0uA3PEdCVvfTEC6x7aI5cPhabHZcH2F+IjJPFHevnfUsVHbVUtt1Naj5 x4IQbl99sFDEV93iN72KMxgie8zTqOxWvc/Sgit6vkN2TNWQk+NJSTAxUUBf3zXznElz itzCCYjMjTl9IBL3ChuK+Y/abRfdQC9zizhh6MI4kAz2jUep9n4gWQg8nLhdBKHb2IWK /ovwJ8RttJRj9kQOEpkfUTBqC21SIGljjdKO50cXUyvKF/nagyzqKgf0K2CqBIt9iDYu DKUw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@aj.id.au header.s=fm2 header.b=ad5a9Zda; dkim=pass header.i=@messagingengine.com header.s=fm2 header.b=14dqTf2+; 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 l4si5655320otf.195.2020.04.04.23.57.46; Sat, 04 Apr 2020 23:57:59 -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; dkim=pass header.i=@aj.id.au header.s=fm2 header.b=ad5a9Zda; dkim=pass header.i=@messagingengine.com header.s=fm2 header.b=14dqTf2+; 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 S1726390AbgDEG5Q (ORCPT + 99 others); Sun, 5 Apr 2020 02:57:16 -0400 Received: from out2-smtp.messagingengine.com ([66.111.4.26]:51675 "EHLO out2-smtp.messagingengine.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726236AbgDEG5Q (ORCPT ); Sun, 5 Apr 2020 02:57:16 -0400 Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.nyi.internal (Postfix) with ESMTP id 6E09B5C0004; Sun, 5 Apr 2020 02:57:15 -0400 (EDT) Received: from imap2 ([10.202.2.52]) by compute3.internal (MEProxy); Sun, 05 Apr 2020 02:57:15 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=aj.id.au; h= mime-version:message-id:in-reply-to:references:date:from:to:cc :subject:content-type; s=fm2; bh=A9dbn5+Kyg5hHH3Cxnfh6Nqgtjiyajy p0XRJXLne8is=; b=ad5a9Zda845H8koTB0ERR7JZxprs0GdpMrwpRMZ7fZWSnYI 7eL/bbCcC+dym83H2P2dMsjdkNQXWhpiH56vVsuP0kuaR/JgLwRTXKOOSww4Zbad xvqqV2oxA9ChQ+ljCKM/YmubHRPvb/ST9VNqC9zQfqHn1YgTMzUcuCdHFdPEkxph /gYZ71NE6Cupf59BzfE2aWpGRRAswj2whckDWzral6e+f0P8t1V9xzUZrhdNPXKT buYxT9RhPUsQKJ38t8yy7nu240JigMpJNxh8QpHgpMHtl//2gqX7uP9zVBpopcHA Ik9ySMGJRLydoSeJ78IiVopBvdt4OV9Qm9uuc+Q== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm2; bh=A9dbn5 +Kyg5hHH3Cxnfh6Nqgtjiyajyp0XRJXLne8is=; b=14dqTf2+KbmRafna3KiVl5 zzDeN6LUsvzS4hfOmtaXgtf3n0fvyXYWVEpRQ7MrszpbM606GKp6iFMH3gIUzfIy GkhSszW5H835rdIlDy3GylDdSP6ZHj6RHxuc/oH8oRlJhq6uuRvjBnRF1BdesFCP dBBvhzCCC6VkXw3TAgLjp7UOe16IQVo0vDDXePVUqiwcO2sbYN0WYqyxGrqzdEOp vpmZHJXP8cq7wHz+gvH59U6o2dIb3gdzNNjlDujJHAnwhQUptOBT2mwbv5rtwR9J 3wIyAd9MLwYlxKg1s6mAmB5J8w/h3BoaAyF92MokFwXnHeUNa5v75/cw5L1FjUjA == X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduhedruddtgddukecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpefofgggkfgjfhffhffvufgtsehttdertderredtnecuhfhrohhmpedftehnughr vgifucflvghffhgvrhihfdcuoegrnhgurhgvfiesrghjrdhiugdrrghuqeenucevlhhush htvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpegrnhgurhgvfiesrghj rdhiugdrrghu X-ME-Proxy: Received: by mailuser.nyi.internal (Postfix, from userid 501) id 62711E00B1; Sun, 5 Apr 2020 02:57:14 -0400 (EDT) X-Mailer: MessagingEngine.com Webmail Interface User-Agent: Cyrus-JMAP/3.1.7-1082-g13d7805-fmstable-20200403v1 Mime-Version: 1.0 Message-Id: <73c7b292-fa99-4809-a0fa-b3605f35aff4@www.fastmail.com> In-Reply-To: References: <20200402194955.16643-1-eajames@linux.ibm.com> <8ca08ea0-2f3e-4b44-a595-bfe96ca02b3f@www.fastmail.com> Date: Sun, 05 Apr 2020 16:27:35 +0930 From: "Andrew Jeffery" To: "Eddie James" , linux-aspeed@lists.ozlabs.org Cc: linux-kernel@vger.kernel.org, devicetree@vger.kernel.org, "Rob Herring" , "Joel Stanley" Subject: Re: [PATCH v7 0/5] soc: aspeed: Add XDMA engine driver Content-Type: text/plain Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sat, 4 Apr 2020, at 01:22, Eddie James wrote: > > On 4/2/20 7:32 PM, Andrew Jeffery wrote: > > > > On Fri, 3 Apr 2020, at 06:19, Eddie James wrote: > >> This series adds a driver to control the Aspeed XDMA engine embedded in the > >> AST2500 and AST2600. The XDMA engine performs automatic DMA operations > >> over PCI-E between the Aspeed SOC (acting as a BMC) and a host processor. > >> > >> Changes since v6: > >> - See individual patches > > v7 is not an evolution on v6 - v7 contains a bunch of bugs that v6 fixed (at least > > wrt locking). How did you generate this series? > > > My goodness, I could have sworn that was v6. I took the series that was > merged in the openbmc kernel. Must have gotten mixed up. -_- No worries, hopefully v8 is in the right state :) > > > > > > Also my name is misspelled in each of the Reviewed-by: tags which makes me > > think that something has gone quite wrong with the posting of v7, and I'm > > concerned that this was based on e.g. v5 but with my tags against v6 applied. > > > Well thats because I added them manually since they had "disappeared" or > so I thought from v6 during the application to openbmc... guess that > should have been a warning sign It certainly was for me! Cheers, Andrew