From: Fabio Estevam <festevam@gmail.com>
To: Sebastian Reichel <sre@kernel.org>
Cc: Stefan Moring <stefanmoring@gmail.com>,
broonie@kernel.org, shawnguo@kernel.org, s.hauer@pengutronxi.de,
linux-imx@nxmp.com, linux-psi@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/1] spi: imx: take in account bits per word instead of assuming 8-bits
Date: Mon, 18 Sep 2023 09:48:36 -0300 [thread overview]
Message-ID: <CAOMZO5CFEZ1BCccQfCtA+j0x_u+95NH66ZmpaerOUNgkh2knpA@mail.gmail.com> (raw)
In-Reply-To: <20230917184720.wzigwjk4v5wakmz6@mercury.elektranox.org>
Hi Stefan,
There is a typo in the spi mailing list. It should be linux-spi@vger.kernel.org.
On Sun, Sep 17, 2023 at 3:47 PM Sebastian Reichel <sre@kernel.org> wrote:
>
> Hi,
>
> On Sun, Sep 17, 2023 at 06:40:37PM +0200, Stefan Moring wrote:
> > The IMX spi driver has a hardcoded 8, breaking the driver for word
> > lengths other than 8.
> >
> > Signed-off-by: Stefan Moring <stefanmoring@gmail.com>
> > ---
>
> patch subject is missing the 'spi: imx:' prefix. Otherwise:
>
> Reported-by: Sebastian Reichel <sre@kernel.org>
> Fixes: 15a6af94a277 ("spi: Increase imx51 ecspi burst length based on transfer length")
> Tested-by: Sebastian Reichel <sre@kernel.org>
With the above tags added and the Subject line fixed:
Reviewed-by: Fabio Estevam <festevam@gmail.com>
_______________________________________________
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:[~2023-09-18 12:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-17 16:40 [PATCH 1/1] take in account bits per word instead of assuming 8-bits Stefan Moring
2023-09-17 18:47 ` [PATCH 1/1] spi: imx: " Sebastian Reichel
2023-09-18 12:48 ` Fabio Estevam [this message]
2023-09-18 15:45 ` [PATCH 1/1] " Mark Brown
-- strict thread matches above, loose matches on Subject: below --
2023-09-18 15:36 [PATCH 1/1] spi: imx: " Stefan Moring
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=CAOMZO5CFEZ1BCccQfCtA+j0x_u+95NH66ZmpaerOUNgkh2knpA@mail.gmail.com \
--to=festevam@gmail.com \
--cc=broonie@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxmp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-psi@vger.kernel.org \
--cc=s.hauer@pengutronxi.de \
--cc=shawnguo@kernel.org \
--cc=sre@kernel.org \
--cc=stefanmoring@gmail.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).