From: Sudeep Holla <sudeep.holla@arm.com>
To: ARM SoC Team <arm@kernel.org>, SoC Team <soc@kernel.org>,
ALKML <linux-arm-kernel@lists.infradead.org>
Cc: Arnd Bergmann <arnd@kernel.org>,
Lorenzo Pieralisi <lpieralisi@kernel.org>,
Kevin Hilman <khilman@kernel.org>,
Liviu Dudau <liviu.dudau@arm.com>
Subject: Re: [GIT PULL] ARM: vexpress: Update for v6.10
Date: Mon, 3 Jun 2024 13:43:30 +0100 [thread overview]
Message-ID: <Zl26clRRMuJNovza@bogus> (raw)
In-Reply-To: <20240515093334.1946888-1-sudeep.holla@arm.com>
On Wed, May 15, 2024 at 10:33:34AM +0100, Sudeep Holla wrote:
> Hi ARM SoC Team,
>
> There is no reason to delay this until v6.11, hence the late pull request
> for v6.10.
>
> Please pull if there is a plan for another late pull request during the
> merge window. Or else it can be deferred for v6.11
>
Please ignore this as it its already -rc2 now. I have now rebased and
will send it as part of v6.11 pull request.
--
Regards,
Sudeep
prev parent reply other threads:[~2024-06-03 12:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-15 9:33 [GIT PULL] ARM: vexpress: Update for v6.10 Sudeep Holla
2024-06-03 12:43 ` Sudeep Holla [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=Zl26clRRMuJNovza@bogus \
--to=sudeep.holla@arm.com \
--cc=arm@kernel.org \
--cc=arnd@kernel.org \
--cc=khilman@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=liviu.dudau@arm.com \
--cc=lpieralisi@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 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).