From: Mark Brown <broonie@kernel.org>
To: Quanyang Wang <quanyang.wang@windriver.com>
Cc: Amit Kumar Mahapatra <amit.kumar-mahapatra@xilinx.com>,
Michal Simek <michal.simek@xilinx.com>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, linux-spi@vger.kernel.org
Subject: Re: [PATCH 0/5] spi: spi-zynqmp-gqspi: fix spi issues
Date: Fri, 16 Apr 2021 17:33:41 +0100 [thread overview]
Message-ID: <20210416163341.GJ5560@sirena.org.uk> (raw)
In-Reply-To: <fb308dee-6ca4-e2de-964a-f67684f15e54@windriver.com>
[-- Attachment #1: Type: text/plain, Size: 210 bytes --]
On Sat, Apr 17, 2021 at 12:31:44AM +0800, Quanyang Wang wrote:
> Sorry for any confusion caused.
No worries, it's mainly just an issue for anyone doing stable backports
- hopefully they'll figure things out.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2021-04-16 16:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-16 14:20 [V2][PATCH 0/5] spi: spi-zynqmp-gqspi: fix spi issues quanyang.wang
2021-04-16 14:20 ` [V2][PATCH 1/5] spi: spi-zynqmp-gqspi: fix clk_enable/disable imbalance issue quanyang.wang
2021-04-16 14:20 ` [V2][PATCH 2/5] spi: spi-zynqmp-gqspi: fix hang issue when suspend/resume quanyang.wang
2021-04-16 14:20 ` [V2][PATCH 3/5] spi: spi-zynqmp-gqspi: Resolved slab-out-of-bounds bug quanyang.wang
2021-04-16 14:20 ` [V2][PATCH 4/5] spi: spi-zynqmp-gqspi: fix use-after-free in zynqmp_qspi_exec_op quanyang.wang
2021-04-16 14:20 ` [V2][PATCH 5/5] spi: spi-zynqmp-gqspi: return -ENOMEM if dma_map_single fails quanyang.wang
2021-04-16 16:01 ` [PATCH 0/5] spi: spi-zynqmp-gqspi: fix spi issues Mark Brown
2021-04-16 16:31 ` Quanyang Wang
2021-04-16 16:33 ` Mark Brown [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-04-16 0:46 quanyang.wang
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=20210416163341.GJ5560@sirena.org.uk \
--to=broonie@kernel.org \
--cc=amit.kumar-mahapatra@xilinx.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=michal.simek@xilinx.com \
--cc=quanyang.wang@windriver.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).