From: Olof Johansson <olof@lixom.net>
To: Sudeep Holla <sudeep.holla@arm.com>
Cc: ARM SoC Team <arm@kernel.org>, SoC Team <soc@kernel.org>,
ALKML <linux-arm-kernel@lists.infradead.org>,
Arnd Bergmann <arnd@kernel.org>,
Cristian Marussi <cristian.marussi@arm.com>
Subject: Re: [GIT PULL] firmware: arm_scmi: Updates for v5.17
Date: Sat, 8 Jan 2022 12:24:10 -0800 [thread overview]
Message-ID: <20220108202410.GA1057@lx2k> (raw)
In-Reply-To: <20220107113740.f4zlz25largdjcfd@bogus>
On Fri, Jan 07, 2022 at 11:37:40AM +0000, Sudeep Holla wrote:
>
> Hi again,
>
> On Wed, Dec 22, 2021 at 02:13:42PM +0000, Sudeep Holla wrote:
> > Hi ARM SoC Team,
> >
> > Please pull !
> >
>
> I am aware I sent this pull request just around the same time Arnd finalised
> the initial set. I have seen emails suggesting that Olof might be planning
> to merge additional PR, so it would be great if this gets included in
> that cut. All the changes are in -next since 21st December, so there should
> be no surprises.
>
> Thanks again and sorry for nagging.
Yeah, no worries -- I'd been letting pull requests sitting for a while over the
holidays. I've merged this into our late branch now.
Thanks,
-Olof
WARNING: multiple messages have this Message-ID (diff)
From: Olof Johansson <olof@lixom.net>
To: Sudeep Holla <sudeep.holla@arm.com>
Cc: ARM SoC Team <arm@kernel.org>, SoC Team <soc@kernel.org>,
ALKML <linux-arm-kernel@lists.infradead.org>,
Arnd Bergmann <arnd@kernel.org>,
Cristian Marussi <cristian.marussi@arm.com>
Subject: Re: [GIT PULL] firmware: arm_scmi: Updates for v5.17
Date: Sat, 8 Jan 2022 12:24:10 -0800 [thread overview]
Message-ID: <20220108202410.GA1057@lx2k> (raw)
In-Reply-To: <20220107113740.f4zlz25largdjcfd@bogus>
On Fri, Jan 07, 2022 at 11:37:40AM +0000, Sudeep Holla wrote:
>
> Hi again,
>
> On Wed, Dec 22, 2021 at 02:13:42PM +0000, Sudeep Holla wrote:
> > Hi ARM SoC Team,
> >
> > Please pull !
> >
>
> I am aware I sent this pull request just around the same time Arnd finalised
> the initial set. I have seen emails suggesting that Olof might be planning
> to merge additional PR, so it would be great if this gets included in
> that cut. All the changes are in -next since 21st December, so there should
> be no surprises.
>
> Thanks again and sorry for nagging.
Yeah, no worries -- I'd been letting pull requests sitting for a while over the
holidays. I've merged this into our late branch now.
Thanks,
-Olof
_______________________________________________
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-01-08 20:30 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-22 14:13 [GIT PULL] firmware: arm_scmi: Updates for v5.17 Sudeep Holla
2021-12-22 14:13 ` Sudeep Holla
2022-01-07 11:37 ` Sudeep Holla
2022-01-07 11:37 ` Sudeep Holla
2022-01-08 20:24 ` Olof Johansson [this message]
2022-01-08 20:24 ` Olof Johansson
2022-02-08 10:00 ` Arnd Bergmann
2022-02-08 10:00 ` Arnd Bergmann
2022-02-08 10:33 ` Sudeep Holla
2022-02-08 10:33 ` Sudeep Holla
2022-02-08 11:14 ` Arnd Bergmann
2022-02-08 11:14 ` Arnd Bergmann
2022-02-08 11:34 ` Sudeep Holla
2022-02-08 11:34 ` Sudeep Holla
2022-01-08 22:00 ` 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=20220108202410.GA1057@lx2k \
--to=olof@lixom.net \
--cc=arm@kernel.org \
--cc=arnd@kernel.org \
--cc=cristian.marussi@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=soc@kernel.org \
--cc=sudeep.holla@arm.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 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.