From: Mirko Vogt <mirko-dev|linux@nanl.de>
To: Ralf Schlatterbeck <rsc@runtux.com>, Mark Brown <broonie@kernel.org>
Cc: Andre Przywara <andre.przywara@arm.com>,
Maxime Ripard <mripard@kernel.org>, Chen-Yu Tsai <wens@csie.org>,
Jernej Skrabec <jernej.skrabec@gmail.com>,
linux-spi@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-sunxi@lists.linux.dev, linux-kernel@vger.kernel.org,
Mirko Vogt <mirko-dev|linux@nanl.de>
Subject: Re: [PATCH 1/1] spi-sun6i: Fix chipselect/clock bug
Date: Sat, 5 Jun 2021 16:06:10 +0200 [thread overview]
Message-ID: <0418aba2-6bca-8de1-9f72-2fb10007fc81@nanl.de> (raw)
In-Reply-To: <20210527113920.ncpzrpst2d6rij3t@runtux.com>
On 5/27/21 1:39 PM, Ralf Schlatterbeck wrote
> OK, let me know if I should repost in new thread with increased version
> number in the subjec
Assuming this wasn't answered yet: was this just a comment for further
patches and things are going their way or should it indeed be resent as
new thread/version with respective changes applied?
Can I do something to help / resolve this?
Have a nice weekend
mirko
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2021-06-05 14:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-20 10:06 [PATCH 1/1] spi-sun6i: Fix chipselect/clock bug Ralf Schlatterbeck
2021-05-21 16:30 ` Andre Przywara
2021-05-21 20:16 ` Ralf Schlatterbeck
2021-05-21 20:19 ` Ralf Schlatterbeck
2021-05-24 12:33 ` Andre Przywara
2021-05-24 16:24 ` Ralf Schlatterbeck
2021-05-25 14:35 ` Mark Brown
2021-05-27 11:39 ` Ralf Schlatterbeck
2021-06-05 14:06 ` Mirko Vogt [this message]
2021-06-14 14:47 ` Ralf Schlatterbeck
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=0418aba2-6bca-8de1-9f72-2fb10007fc81@nanl.de \
--to=mirko-dev|linux@nanl.de \
--cc=andre.przywara@arm.com \
--cc=broonie@kernel.org \
--cc=jernej.skrabec@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=linux-sunxi@lists.linux.dev \
--cc=mripard@kernel.org \
--cc=rsc@runtux.com \
--cc=wens@csie.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;
as well as URLs for NNTP newsgroup(s).