From: Serge Semin <fancer.lancer@gmail.com>
To: Mark Brown <broonie@kernel.org>
Cc: linux-spi@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
Abe Kohandel <abe.kohandel@intel.com>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Subject: Re: [PATCH 0/2] spi: dw: Add compatible for Intel Mount Evans SoC
Date: Tue, 6 Jun 2023 20:33:12 +0300 [thread overview]
Message-ID: <20230606173312.wfrowqc7irecow2s@mobilestation> (raw)
In-Reply-To: <7696b01e-c388-45f2-9694-e427dde84b2b@sirena.org.uk>
On Tue, Jun 06, 2023 at 05:47:40PM +0100, Mark Brown wrote:
> On Tue, Jun 06, 2023 at 07:40:40PM +0300, Serge Semin wrote:
>
> > Mark, next time please wait at least for a few days before applying.
> > Give me a chance to review.)
>
> It's a trivial quirk for a platform, it seemed more hassle to wait TBH.
>
> > * In this case I have had a question regarding the in-code comment
> > which may have been needed to be fixed a bit.
>
> That can always be fixed incrementally if there's issues.
Ok. I've sent my comment in that regards. Let's see what the author
responds.
-Serge(y)
prev parent reply other threads:[~2023-06-06 17:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-06 14:54 [PATCH 0/2] spi: dw: Add compatible for Intel Mount Evans SoC Abe Kohandel
2023-06-06 14:54 ` [PATCH 1/2] " Abe Kohandel
2023-06-06 17:28 ` Serge Semin
2023-06-06 19:07 ` Abe Kohandel
2023-06-06 19:13 ` Serge Semin
2023-06-06 23:21 ` Abe Kohandel
2023-06-06 14:54 ` [PATCH 2/2] dt-bindings: spi: snps,dw-apb-ssi: " Abe Kohandel
2023-06-06 16:24 ` [PATCH 0/2] spi: dw: " Mark Brown
2023-06-06 16:40 ` Serge Semin
2023-06-06 16:47 ` Mark Brown
2023-06-06 17:33 ` Serge Semin [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=20230606173312.wfrowqc7irecow2s@mobilestation \
--to=fancer.lancer@gmail.com \
--cc=abe.kohandel@intel.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=robh+dt@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.