[PATCH v7 6/8] PCI/VGA: Introduce is_boot_device function callback to vga_client_register
Bjorn Helgaas
helgaas at kernel.org
Fri Jun 30 17:41:56 UTC 2023
On Fri, Jun 30, 2023 at 10:14:11AM +0800, suijingfeng wrote:
> On 2023/6/30 01:44, Limonciello, Mario wrote:
> > > On 2023/6/29 23:54, Bjorn Helgaas wrote:
> > > > On Thu, Jun 22, 2023 at 01:08:15PM +0800, Sui Jingfeng wrote:
> > > > 4) Right now we're in the middle of the v6.5 merge window, so new
> > > > content, e.g., this series, is too late for v6.5. Most
> > > > maintainers, including me, wait to merge new content until the
> > > > merge window closes and a new -rc1 is tagged. This merge window
> > > > should close on July 9, and people will start merging content for
> > > > v6.6, typically based on v6.5-rc1.
> > >
> > > Would you will merge all of the patches in this series (e.g. including
> > > the patch for drm/amdgpu(7/8) and drm/radeon(8/8)) ?
> > >
> > > Or just part of them?
The bulk of this series is drivers/pci changes, so typically I would
merge all the patches after getting Acked-by tags from the other
subsystems (DRM and VFIO).
> Is it possible to merge the PCI/VGA part as fast as possible,
> especially the PATCH-0006 PCI/VGA: Introduce is_boot_device function
> callback to vga_client_register
We're in the middle of the v6.5 merge window, so it's too late to add
things to v6.5-rc1. The most likely path for new material like this
would be to queue it for v6.6, which means I would merge it after
v6.5-rc1 is tagged (that tag will probably happen on July 9).
It would then be in -next until the v6.6 merge window opens (likely in
September), when it would be merged into Linus' tree.
If the series fixes a regression or other major defect, it's
*possible* to merge things earlier, so they appear in v6.5. But this
series doesn't seem to fall in that category, so I think v6.6 is a
more realistic target.
Merging for v6.6 would include both the PCI parts and the DRM parts at
the same time, so hopefully that addresses your dependency concerns.
I suggest that you wait until v6.5-rc1, rebase your patches so they
apply cleanly on that tag, collect all the Reviewed-by and Acked-by
tags, include them in your commit logs, and then repost them.
Bjorn
More information about the dri-devel
mailing list