From: "Arnd Bergmann" <arnd@arndb.de>
To: patchwork-bot+linux-soc <patchwork-bot+linux-soc@kernel.org>,
"Neil Armstrong" <neil.armstrong@linaro.org>
Cc: soc@kernel.org
Subject: Re: [GIT PULL] amlogic Drivers updates for v6.2
Date: Wed, 23 Nov 2022 12:05:50 +0100 [thread overview]
Message-ID: <894fa542-bb95-4fad-971e-30f133ae2c46@app.fastmail.com> (raw)
In-Reply-To: <166915562582.11152.9314638583392404867.git-patchwork-notify@kernel.org>
On Tue, Nov 22, 2022, at 23:20, patchwork-bot+linux-soc@kernel.org wrote:
> Hello:
>
> This pull request was applied to soc/soc.git (for-next)
> by Arnd Bergmann <arnd@arndb.de>:
>
> On Tue, 22 Nov 2022 16:24:59 +0100 you wrote:
>> Hi,
>>
>> Here's an Amlogic Drivers change for v6.3, fixes memcpy vs iomem type warnings in meson_sm driver.
>>
>> Neil
>>
>> The following changes since commit 9abf2313adc1ca1b6180c508c25f22f9395cc780:
>>
>> [...]
>
> Here is the summary with links:
> - [GIT,PULL] amlogic Drivers updates for v6.2
> https://git.kernel.org/soc/soc/c/ad654a0a21bb
>
> You are awesome, thank you!
> --
Sorry about this, I meant to remove this change when I originally
complained about this, and it looked I accidentally kept working
on the branch that still had it. I've fixed it up now, and it's
gone again once I push out the latest updaet.
Arnd
prev parent reply other threads:[~2022-11-23 11:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-22 15:24 [GIT PULL] amlogic Drivers updates for v6.2 Neil Armstrong
2022-11-22 15:24 ` Neil Armstrong
2022-11-22 15:24 ` Neil Armstrong
2022-11-22 21:48 ` Arnd Bergmann
2022-11-22 21:48 ` Arnd Bergmann
2022-11-22 21:48 ` Arnd Bergmann
2022-11-23 10:51 ` Neil Armstrong
2022-11-23 10:51 ` Neil Armstrong
2022-11-23 10:51 ` Neil Armstrong
2022-11-22 22:20 ` patchwork-bot+linux-soc
2022-11-23 11:05 ` Arnd Bergmann [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=894fa542-bb95-4fad-971e-30f133ae2c46@app.fastmail.com \
--to=arnd@arndb.de \
--cc=neil.armstrong@linaro.org \
--cc=patchwork-bot+linux-soc@kernel.org \
--cc=soc@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.