From: Arnd Bergmann <arnd@arndb.de>
To: "hasegawa-hitomi@fujitsu.com" <hasegawa-hitomi@fujitsu.com>
Cc: Arnd Bergmann <arnd@arndb.de>, "olof@lixom.net" <olof@lixom.net>,
"catalin.marinas@arm.com" <catalin.marinas@arm.com>,
"will@kernel.org" <will@kernel.org>,
"sumit.garg@linaro.org" <sumit.garg@linaro.org>,
"gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
"jirislaby@kernel.org" <jirislaby@kernel.org>,
"daniel.thompson@linaro.org" <daniel.thompson@linaro.org>,
"dianders@chromium.org" <dianders@chromium.org>,
"soc@kernel.org" <soc@kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v5 0/1] soc: fujitsu: Add A64FX diagnostic interrupt driver
Date: Mon, 18 Jul 2022 13:39:04 +0200 [thread overview]
Message-ID: <CAK8P3a14-j_EKpssvZaKar-vf2=BcLD-Dxzq8dhca9fqtobwgw@mail.gmail.com> (raw)
In-Reply-To: <OSZPR01MB7050362B7F7B072AF5304A4DEBAC9@OSZPR01MB7050.jpnprd01.prod.outlook.com>
On Thu, Jun 16, 2022 at 11:02 AM hasegawa-hitomi@fujitsu.com
<hasegawa-hitomi@fujitsu.com> wrote:
>
> Hi Arnd,
>
> There seems to be no comment in particular, but what should I do
> in order to be accepted?
Sorry for the delay, I was planning to apply it last month and it fell
through the cracks.
Found it again while going through my backlog and applied your patch to the
arm/drivers branch of the soc tree. It should be part of the linu-next tree from
tomorrow and my pull requests for the coming merge window.
Arnd
WARNING: multiple messages have this Message-ID (diff)
From: Arnd Bergmann <arnd@arndb.de>
To: "hasegawa-hitomi@fujitsu.com" <hasegawa-hitomi@fujitsu.com>
Cc: Arnd Bergmann <arnd@arndb.de>, "olof@lixom.net" <olof@lixom.net>,
"catalin.marinas@arm.com" <catalin.marinas@arm.com>,
"will@kernel.org" <will@kernel.org>,
"sumit.garg@linaro.org" <sumit.garg@linaro.org>,
"gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
"jirislaby@kernel.org" <jirislaby@kernel.org>,
"daniel.thompson@linaro.org" <daniel.thompson@linaro.org>,
"dianders@chromium.org" <dianders@chromium.org>,
"soc@kernel.org" <soc@kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v5 0/1] soc: fujitsu: Add A64FX diagnostic interrupt driver
Date: Mon, 18 Jul 2022 13:39:04 +0200 [thread overview]
Message-ID: <CAK8P3a14-j_EKpssvZaKar-vf2=BcLD-Dxzq8dhca9fqtobwgw@mail.gmail.com> (raw)
In-Reply-To: <OSZPR01MB7050362B7F7B072AF5304A4DEBAC9@OSZPR01MB7050.jpnprd01.prod.outlook.com>
On Thu, Jun 16, 2022 at 11:02 AM hasegawa-hitomi@fujitsu.com
<hasegawa-hitomi@fujitsu.com> wrote:
>
> Hi Arnd,
>
> There seems to be no comment in particular, but what should I do
> in order to be accepted?
Sorry for the delay, I was planning to apply it last month and it fell
through the cracks.
Found it again while going through my backlog and applied your patch to the
arm/drivers branch of the soc tree. It should be part of the linu-next tree from
tomorrow and my pull requests for the coming merge window.
Arnd
_______________________________________________
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:[~2022-07-18 13:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-20 7:41 [PATCH v5 0/1] soc: fujitsu: Add A64FX diagnostic interrupt driver Hitomi Hasegawa
2022-05-20 7:41 ` Hitomi Hasegawa
2022-05-20 7:41 ` [PATCH v5 1/1] " Hitomi Hasegawa
2022-05-20 7:41 ` Hitomi Hasegawa
2022-06-09 7:48 ` [PATCH v5 0/1] " hasegawa-hitomi
2022-06-09 7:48 ` hasegawa-hitomi
2022-06-16 9:02 ` hasegawa-hitomi
2022-06-16 9:02 ` hasegawa-hitomi
2022-07-18 11:39 ` Arnd Bergmann [this message]
2022-07-18 11:39 ` Arnd Bergmann
2022-07-19 14:10 ` patchwork-bot+linux-soc
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='CAK8P3a14-j_EKpssvZaKar-vf2=BcLD-Dxzq8dhca9fqtobwgw@mail.gmail.com' \
--to=arnd@arndb.de \
--cc=catalin.marinas@arm.com \
--cc=daniel.thompson@linaro.org \
--cc=dianders@chromium.org \
--cc=gregkh@linuxfoundation.org \
--cc=hasegawa-hitomi@fujitsu.com \
--cc=jirislaby@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=olof@lixom.net \
--cc=soc@kernel.org \
--cc=sumit.garg@linaro.org \
--cc=will@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.