From: Florian Fainelli <florian.fainelli@broadcom.com>
To: "Jonas Gorski" <jonas.gorski@gmail.com>,
"William Zhang" <william.zhang@broadcom.com>,
"Kursad Oney" <kursad.oney@broadcom.com>,
"Broadcom internal kernel review list"
<bcm-kernel-feedback-list@broadcom.com>,
"Mark Brown" <broonie@kernel.org>,
"Anand Gore" <anand.gore@broadcom.com>,
"Florian Fainelli" <f.fainelli@gmail.com>,
"Rafał Miłecki" <rafal@milecki.pl>
Cc: linux-spi@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 2/3] spi: bcm{63xx,bca}-hsspi: update my email address
Date: Tue, 4 Jul 2023 07:47:46 -0700 [thread overview]
Message-ID: <33bea073-50e1-61fa-4b08-4b059f4e69df@broadcom.com> (raw)
In-Reply-To: <20230630202257.8449-2-jonas.gorski@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 266 bytes --]
On 6/30/2023 10:22 PM, Jonas Gorski wrote:
> Update my email address to a working one, as the openwrt.org one is
> broken since ages.
>
> Signed-off-by: Jonas Gorski <jonas.gorski@gmail.com>
Acked-by: Florian Fainelli <florian.fainelli@broadcom.com>
--
Florian
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4221 bytes --]
next prev parent reply other threads:[~2023-07-04 14:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-30 20:22 [PATCH 1/3] MAINTAINERS: add myself for spi-bcm63xx Jonas Gorski
2023-06-30 20:22 ` [PATCH 2/3] spi: bcm{63xx,bca}-hsspi: update my email address Jonas Gorski
2023-07-04 0:33 ` William Zhang
2023-07-04 14:47 ` Florian Fainelli [this message]
2023-06-30 20:22 ` [PATCH 3/3] mailmap: add entry for Jonas Gorski Jonas Gorski
2023-06-30 20:30 ` [PATCH 1/3] MAINTAINERS: add myself for spi-bcm63xx Jonas Gorski
2023-07-04 15:42 ` (subset) " Mark Brown
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=33bea073-50e1-61fa-4b08-4b059f4e69df@broadcom.com \
--to=florian.fainelli@broadcom.com \
--cc=anand.gore@broadcom.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=broonie@kernel.org \
--cc=f.fainelli@gmail.com \
--cc=jonas.gorski@gmail.com \
--cc=kursad.oney@broadcom.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=rafal@milecki.pl \
--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