public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Sudeep Holla <sudeep.holla@arm.com>
To: Jassi Brar <jassisinghbrar@gmail.com>,
	Sudeep Holla <sudeep.holla@arm.com>,
	Stephen Rothwell <sfr@canb.auug.org.au>,
	Mark Brown <broonie@kernel.org>
Cc: linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] Mailbox changes for v6.19
Date: Thu, 15 Jan 2026 10:42:36 +0000	[thread overview]
Message-ID: <aWjEnIfATvipFyKS@bogus> (raw)
In-Reply-To: <CABb+yY2or-wT46Z3jGZ_ks91tHGM2D-1OYeL0xtHfuZURatg9A@mail.gmail.com>

Hi Jassi,

On Wed, Dec 10, 2025 at 09:28:56PM -0600, Jassi Brar wrote:
> Hi Linus,
> The following changes since commit 7d0a66e4bb9081d75c82ec4957c50034cb0ea449:
> 
>   Linux 6.18 (2025-11-30 14:42:10 -0800)
> 
> are available in the Git repository at:
> 
>   git://git.kernel.org/pub/scm/linux/kernel/git/jassibrar/mailbox.git
> tags/mailbox-v6.19
> 
> for you to fetch changes up to 1ec6e0e8c0dd6599472af944b8d703d526ff1031:
> 
>   mailbox: mtk-cmdq: Add driver data to support for MT8196 (2025-12-10
> 17:17:01 -0600)
> 
> ----------------------------------------------------------------
> pcc: refactor and improve initialisation and interrupt handling
> qcom:     enable Kaanapali and Glymur platforms
> renesas:  add MFIS mailbox driver
> mediatek: add mtk-vcp-mailbox driver and bindings
>           add support for MT8196 into mtk-cmdq
> misc:     remove unneeded double quotation in Kconfig
>           drop POLARFIRE from ARCH_MICROCHIP_POLARFIRE
>           fix out-of-bounds access in mchp_ipc_get_cluster_aggr_irq
> 
> ----------------------------------------------------------------


All these changes that were missed in the v6.19 merge window were accidentally
dropped from your -next(and hence the linux-next tree), I suppose, as they
were present until about 10 days ago. This is not ideal, and the pull request
may get rejected again if they are not in -next for some time before the next
merge window.

Could you please have a look at it?.

-- 
Regards,
Sudeep

  parent reply	other threads:[~2026-01-15 10:42 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-10 23:31 [GIT PULL] Mailbox changes for v6.19 Jassi Brar
2025-12-11  0:23 ` Stephen Rothwell
2025-12-11  3:30   ` Jassi Brar
2025-12-11  3:28 ` Jassi Brar
2025-12-11  3:44   ` Linus Torvalds
2026-01-15 10:42   ` Sudeep Holla [this message]
2026-01-14  8:36 ` Jingyi Wang

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=aWjEnIfATvipFyKS@bogus \
    --to=sudeep.holla@arm.com \
    --cc=broonie@kernel.org \
    --cc=jassisinghbrar@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    /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