From: Mark Brown <broonie@kernel.org>
To: Nikita Shubin <nikita.shubin@maquefel.me>
Cc: Alexander Sverdlin <alexander.sverdlin@gmail.com>,
Geert Uytterhoeven <geert@linux-m68k.org>,
"open list:SPI SUBSYSTEM" <linux-spi@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2/8] spi: spi-ep93xx: Prepare clock before using it
Date: Mon, 26 Jul 2021 13:01:08 +0100 [thread overview]
Message-ID: <20210726120108.GG4670@sirena.org.uk> (raw)
In-Reply-To: <20210726115058.23729-3-nikita.shubin@maquefel.me>
[-- Attachment #1: Type: text/plain, Size: 433 bytes --]
On Mon, Jul 26, 2021 at 02:50:46PM +0300, Nikita Shubin wrote:
> spi_master spi0: failed to prepare transfer hardware: -108
>
> Signed-off-by: Alexander Sverdlin <alexander.sverdlin@gmail.com>
> ---
> drivers/spi/spi-ep93xx.c | 4 ++--
You've not provided a Signed-off-by for this so I can't do anything with
it, please see Documentation/process/submitting-patches.rst for details
on what this is and why it's important.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2021-07-26 12:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-26 11:50 [PATCH 0/8] arm: ep93xx: CCF conversion Nikita Shubin
2021-07-26 11:50 ` [PATCH 2/8] spi: spi-ep93xx: Prepare clock before using it Nikita Shubin
2021-07-26 12:01 ` Mark Brown [this message]
2021-07-26 13:59 ` [PATCH v2 0/8] arm: ep93xx: CCF conversion Nikita Shubin
2021-07-26 13:59 ` [PATCH v2 2/8] spi: spi-ep93xx: Prepare clock before using it Nikita Shubin
2021-07-26 16:51 ` Mark Brown
2021-08-02 7:36 ` Alexander Sverdlin
2021-09-13 21:36 ` Alexander Sverdlin
2021-09-13 21:37 ` Alexander Sverdlin
2021-09-14 10:32 ` Mark Brown
2021-08-03 22:35 ` (subset) [PATCH v2 0/8] arm: ep93xx: CCF conversion Mark Brown
2021-07-31 22:04 ` [PATCH " Linus Walleij
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=20210726120108.GG4670@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alexander.sverdlin@gmail.com \
--cc=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=nikita.shubin@maquefel.me \
/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).