Re: [PATCH v2 0/2] Fix mmap memory boundary calculation

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Tue, Aug 6, 2024 at 2:08 PM Joonas Lahtinen
<joonas.lahtinen@xxxxxxxxxxxxxxx> wrote:
> Quoting Andi Shyti (2024-08-06 12:46:07)
> > Hi Greg,
> >
> > same question without the stable mailing list not to trigger the
> > automatic reply.
> >
> > > Andi Shyti (2):
> > >   drm/i915/gem: Adjust vma offset for framebuffer mmap offset
> > >   drm/i915/gem: Fix Virtual Memory mapping boundaries calculation
> >
> > I have forgotten to actually Cc the stable mailing list here.
> > These two patches need to be merged together even if only the
> > second patch has the "Fixes:" tag.
> >
> > I could have used the "Requires:" tag, but the commit id would
> > change in between merges and rebases.
>
> The patches were the top two in drm-intel-gt-next and committed
> only few hours ago so I fixed up the patches adding Cc: stable
> and Requires:

I'm not very familiar with how the DRM trees work - shouldn't fixes in
i915 go on the separate drm-intel-fixes branch so that they don't have
to wait for a merge window?




[Index of Archives]     [AMD Graphics]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux