From: Wolfram Sang <wsa@kernel.org>
To: Florian Fainelli <f.fainelli@gmail.com>
Cc: William Zhang <william.zhang@broadcom.com>,
Linux ARM List <linux-arm-kernel@lists.infradead.org>,
Broadcom Kernel List <bcm-kernel-feedback-list@broadcom.com>,
anand.gore@broadcom.com, dan.beygelman@broadcom.com,
kursad.oney@broadcom.com, joel.peshkin@broadcom.com,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Jan Dabros <jsd@semihalf.com>,
Jarkko Nikula <jarkko.nikula@linux.intel.com>,
Jie Deng <jie.deng@intel.com>,
Krzysztof Kozlowski <krzk@kernel.org>,
Lukas Bulwahn <lukas.bulwahn@gmail.com>,
Rob Herring <robh@kernel.org>,
Sam Protsenko <semen.protsenko@linaro.org>,
Sven Peter <sven@svenpeter.dev>, Tyrone Ting <kfting@nuvoton.com>,
linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [RESEND PATCH 5/8] i2c: brcmstb: bcmbca: Replace ARCH_BCM_63XX with ARCH_BCMBCA
Date: Thu, 7 Jul 2022 22:52:09 +0200 [thread overview]
Message-ID: <YsdHeR5JexIjgoUk@shikoro> (raw)
In-Reply-To: <c546adbe-482a-1fe2-039a-b5780a0fdbcf@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 251 bytes --]
> Alternatively, we can merge these patches through the Broadcom ARM SoC pull
> request(s) to ensure they all land at the same time.
That's what I assumed (and also prefer), so I acked the I2C patch. Let
me know, guys, if I should pick it instead.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2022-07-07 20:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220707065800.261269-1-william.zhang@broadcom.com>
2022-07-07 6:57 ` [RESEND PATCH 5/8] i2c: brcmstb: bcmbca: Replace ARCH_BCM_63XX with ARCH_BCMBCA William Zhang
2022-07-07 16:24 ` Florian Fainelli
2022-07-07 20:52 ` Wolfram Sang [this message]
2022-07-08 21:09 ` Florian Fainelli
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=YsdHeR5JexIjgoUk@shikoro \
--to=wsa@kernel.org \
--cc=anand.gore@broadcom.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=dan.beygelman@broadcom.com \
--cc=f.fainelli@gmail.com \
--cc=jarkko.nikula@linux.intel.com \
--cc=jie.deng@intel.com \
--cc=joel.peshkin@broadcom.com \
--cc=jsd@semihalf.com \
--cc=kfting@nuvoton.com \
--cc=krzk@kernel.org \
--cc=kursad.oney@broadcom.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lukas.bulwahn@gmail.com \
--cc=robh@kernel.org \
--cc=semen.protsenko@linaro.org \
--cc=sven@svenpeter.dev \
--cc=william.zhang@broadcom.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).