From: Mark Brown <broonie@kernel.org>
To: Florian Fainelli <florian.fainelli@broadcom.com>
Cc: "Florian Fainelli" <f.fainelli@gmail.com>,
linux-kernel@vger.kernel.org, linux-spi@vger.kernel.org,
"Álvaro Fernández Rojas" <noltari@gmail.com>,
bcm-kernel-feedback-list@broadcom.com, p.zabel@pengutronix.de,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v3 2/4] spi: bcm63xx-spi: allow building for BMIPS
Date: Tue, 16 Jun 2020 19:30:10 +0100 [thread overview]
Message-ID: <20200616183010.GV4447@sirena.org.uk> (raw)
In-Reply-To: <ea904b53-3f6f-da28-39f8-f811f432395a@broadcom.com>
[-- Attachment #1.1: Type: text/plain, Size: 804 bytes --]
On Tue, Jun 16, 2020 at 10:31:16AM -0700, Florian Fainelli wrote:
> On 6/16/2020 10:25 AM, Mark Brown wrote:
> >> In Alvaro's defense, you applied the patches despite me requesting that
> >> specific changes be made (use the optional reset control API variant).
> > I applied only the two patches that you'd acked, not the reset patches
> > which had problems.
> Indeed, sorry for not reading your commit message properly, I believe I
> request that before, cannot the "applied" response just reply with the
> patches *applied* and not *all* part of the series?
You might've mentioned it to someone else using b4 but not me - AFAICT
it's not configurable. I can see arguments either way TBH, but I do
agree that the current output could be confusing and if nothing else the
wording could be better.
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
[-- Attachment #2: Type: text/plain, Size: 176 bytes --]
_______________________________________________
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:[~2020-06-16 18:30 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-16 7:02 [PATCH v3 0/4] spi: bcm63xx: add BMIPS support Álvaro Fernández Rojas
2020-06-16 7:02 ` [PATCH v3 1/4] spi: bcm63xx-spi: add reset support Álvaro Fernández Rojas
2020-06-16 17:05 ` Florian Fainelli
2020-06-16 7:02 ` [PATCH v3 2/4] spi: bcm63xx-spi: allow building for BMIPS Álvaro Fernández Rojas
2020-06-16 17:07 ` Mark Brown
2020-06-16 17:15 ` Florian Fainelli
2020-06-16 17:25 ` Mark Brown
2020-06-16 17:31 ` Florian Fainelli
2020-06-16 18:30 ` Mark Brown [this message]
2020-06-16 7:02 ` [PATCH v3 3/4] spi: bcm63xx-hsspi: add reset support Álvaro Fernández Rojas
2020-06-16 17:07 ` Florian Fainelli
2020-06-16 7:02 ` [PATCH v3 4/4] spi: bcm63xx-hsspi: allow building for BMIPS Álvaro Fernández Rojas
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=20200616183010.GV4447@sirena.org.uk \
--to=broonie@kernel.org \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=f.fainelli@gmail.com \
--cc=florian.fainelli@broadcom.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=noltari@gmail.com \
--cc=p.zabel@pengutronix.de \
/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).