From: Vadym Kochan <vadym.kochan@plvision.eu>
To: Mark Brown <broonie@kernel.org>
Cc: linux-spi@vger.kernel.org, linux-kernel@vger.kernel.org,
Elad Nachman <enachman@marvell.com>, Noam <lnoam@marvell.com>
Subject: Re: [PATCH 4/7] spi: a3700: support BE for AC5 SPI driver
Date: Mon, 25 Jul 2022 15:55:05 +0300 [thread overview]
Message-ID: <20220725125505.GB5304@plvision.eu> (raw)
In-Reply-To: <YtxL2kjJhJ6IhVDA@sirena.org.uk>
Hi Mark,
On Sat, Jul 23, 2022 at 08:28:26PM +0100, Mark Brown wrote:
> On Sat, Jul 23, 2022 at 01:22:37PM +0300, Vadym Kochan wrote:
> > From: Noam <lnoam@marvell.com>
> >
> > Tested-by: Raz Adashi <raza@marvell.com>
> > Reviewed-by: Raz Adashi <raza@marvell.com>
> > Signed-off-by: Vadym Kochan <vadym.kochan@plvision.eu>
> > ---
>
> There's no signoff here from Noam or anyone else at Marvell...
>
Will fix it.
> 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.
Sorry, I picked it from locally generated series, I will send it as
a separate patch because there are no dependencies on other patches.
Thanks!
prev parent reply other threads:[~2022-07-25 12:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-23 10:22 [PATCH 4/7] spi: a3700: support BE for AC5 SPI driver Vadym Kochan
2022-07-23 10:49 ` Christophe JAILLET
2022-07-25 12:52 ` Vadym Kochan
2022-07-23 19:28 ` Mark Brown
2022-07-25 12:55 ` Vadym Kochan [this message]
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=20220725125505.GB5304@plvision.eu \
--to=vadym.kochan@plvision.eu \
--cc=broonie@kernel.org \
--cc=enachman@marvell.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=lnoam@marvell.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).