[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <YtxL2kjJhJ6IhVDA@sirena.org.uk>
Date: Sat, 23 Jul 2022 20:28:26 +0100
From: Mark Brown <broonie@...nel.org>
To: Vadym Kochan <vadym.kochan@...ision.eu>
Cc: linux-spi@...r.kernel.org, linux-kernel@...r.kernel.org,
Elad Nachman <enachman@...vell.com>, Noam <lnoam@...vell.com>
Subject: Re: [PATCH 4/7] spi: a3700: support BE for AC5 SPI driver
On Sat, Jul 23, 2022 at 01:22:37PM +0300, Vadym Kochan wrote:
> From: Noam <lnoam@...vell.com>
>
> Tested-by: Raz Adashi <raza@...vell.com>
> Reviewed-by: Raz Adashi <raza@...vell.com>
> Signed-off-by: Vadym Kochan <vadym.kochan@...ision.eu>
> ---
There's no signoff here from Noam or anyone else at Marvell...
You've not copied me on the rest of the series so I've no idea what's
going on with dependencies. When sending a patch series it is important
to ensure that all the various maintainers understand what the
relationship between the patches as the expecation is that there will be
interdependencies. Either copy everyone on the whole series or at least
copy them on the cover letter and explain what's going on. If there are
no strong interdependencies then it's generally simplest to just send
the patches separately to avoid any possible confusion.
Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)
Powered by blists - more mailing lists