linux-next: Add Tegra fixes branch

linux-next: Add Tegra fixes branch

[Thierry Reding]

[-- Attachment #1: Type: text/plain, Size: 383 bytes --]

Hi Mark,

So far I've been carrying fixes patches as part of the regular for-next
branch, but I'm thinking of changing the process a little bit and having
a separate fixes branch that feeds into linux-next would be cleaner to
separate things.

Can you add this branch:

  https://git.kernel.org/pub/scm/linux/kernel/git/tegra/linux.git#fixes

to linux-next, please?

Thanks,
Thierry

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

Re: linux-next: Add Tegra fixes branch

[Mark Brown]

[-- Attachment #1: Type: text/plain, Size: 1055 bytes --]

On Fri, Aug 28, 2026 at 04:28:41PM +0200, Thierry Reding wrote:

> Can you add this branch:

>   https://git.kernel.org/pub/scm/linux/kernel/git/tegra/linux.git#fixes

> to linux-next, please?

I've updated the configuration, the new tree should appear from Monday.

Thanks for adding your subsystem tree as a participant of linux-next.  As
you may know, this is not a judgement of your code.  The purpose of
linux-next is for integration testing and to lower the impact of
conflicts between subsystems in the next merge window.

You will need to ensure that the patches/commits in your tree/series have
been:
     * submitted under GPL v2 (or later) and include the Contributor's
        Signed-off-by,
     * posted to the relevant mailing list,
     * reviewed by you (or another maintainer of your subsystem tree),
     * successfully unit tested, and
     * destined for the current or next Linux merge window.

Basically, this should be just what you would send to Linus (or ask him
to fetch).  It is allowed to be rebased if you deem it necessary.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]