From: "Andrew Jeffery" <andrew@aj.id.au>
To: "Eddie James" <eajames@linux.ibm.com>, linux-aspeed@lists.ozlabs.org
Cc: linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
"Rob Herring" <robh+dt@kernel.org>,
"Joel Stanley" <joel@jms.id.au>
Subject: Re: [PATCH v7 0/5] soc: aspeed: Add XDMA engine driver
Date: Fri, 03 Apr 2020 11:02:41 +1030 [thread overview]
Message-ID: <8ca08ea0-2f3e-4b44-a595-bfe96ca02b3f@www.fastmail.com> (raw)
In-Reply-To: <20200402194955.16643-1-eajames@linux.ibm.com>
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?
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.
Andrew
next prev parent reply other threads:[~2020-04-03 0:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-02 19:49 Eddie James
2020-04-02 19:49 ` [PATCH v7 1/5] dt-bindings: soc: Add Aspeed XDMA engine Eddie James
2020-04-02 19:49 ` [PATCH v7 2/5] soc: aspeed: Add XDMA Engine Driver Eddie James
2020-04-02 19:49 ` [PATCH v7 3/5] soc: aspeed: xdma: Add user interface Eddie James
2020-04-02 19:49 ` [PATCH v7 4/5] soc: aspeed: xdma: Add reset ioctl Eddie James
2020-04-02 19:49 ` [PATCH v7 5/5] ARM: dts: Aspeed: AST2600: Add XDMA PCI-E root control reset Eddie James
2020-04-03 0:32 ` Andrew Jeffery [this message]
2020-04-03 14:52 ` [PATCH v7 0/5] soc: aspeed: Add XDMA engine driver Eddie James
2020-04-05 6:57 ` Andrew Jeffery
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=8ca08ea0-2f3e-4b44-a595-bfe96ca02b3f@www.fastmail.com \
--to=andrew@aj.id.au \
--cc=devicetree@vger.kernel.org \
--cc=eajames@linux.ibm.com \
--cc=joel@jms.id.au \
--cc=linux-aspeed@lists.ozlabs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@kernel.org \
/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
all inboxes | Powered by JetHome®