lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <MN0PR12MB6101CDB6FF9DC8F8EDEF5F45E225A@MN0PR12MB6101.namprd12.prod.outlook.com>
Date:   Thu, 29 Jun 2023 17:44:09 +0000
From:   "Limonciello, Mario" <Mario.Limonciello@....com>
To:     "15330273260@....cn" <15330273260@....cn>,
        Bjorn Helgaas <helgaas@...nel.org>,
        Sui Jingfeng <suijingfeng@...ngson.cn>
CC:     Bjorn Helgaas <bhelgaas@...gle.com>,
        "linux-fbdev@...r.kernel.org" <linux-fbdev@...r.kernel.org>,
        Cornelia Huck <cohuck@...hat.com>,
        Karol Herbst <kherbst@...hat.com>,
        "nouveau@...ts.freedesktop.org" <nouveau@...ts.freedesktop.org>,
        Joonas Lahtinen <joonas.lahtinen@...ux.intel.com>,
        "dri-devel@...ts.freedesktop.org" <dri-devel@...ts.freedesktop.org>,
        "Chai, Thomas" <YiPeng.Chai@....com>,
        "Gao, Likun" <Likun.Gao@....com>, David Airlie <airlied@...il.com>,
        Ville Syrjala <ville.syrjala@...ux.intel.com>,
        Yi Liu <yi.l.liu@...el.com>,
        "kvm@...r.kernel.org" <kvm@...r.kernel.org>,
        "amd-gfx@...ts.freedesktop.org" <amd-gfx@...ts.freedesktop.org>,
        Jason Gunthorpe <jgg@...pe.ca>,
        Ben Skeggs <bskeggs@...hat.com>,
        "linux-pci@...r.kernel.org" <linux-pci@...r.kernel.org>,
        Kevin Tian <kevin.tian@...el.com>,
        "Lazar, Lijo" <Lijo.Lazar@....com>,
        Thomas Zimmermann <tzimmermann@...e.de>,
        "Zhang, Bokun" <Bokun.Zhang@....com>,
        "intel-gfx@...ts.freedesktop.org" <intel-gfx@...ts.freedesktop.org>,
        Maarten Lankhorst <maarten.lankhorst@...ux.intel.com>,
        Jani Nikula <jani.nikula@...ux.intel.com>,
        Alex Williamson <alex.williamson@...hat.com>,
        Abhishek Sahu <abhsahu@...dia.com>,
        Maxime Ripard <mripard@...nel.org>,
        Rodrigo Vivi <rodrigo.vivi@...el.com>,
        Tvrtko Ursulin <tvrtko.ursulin@...ux.intel.com>,
        Yishai Hadas <yishaih@...dia.com>,
        "Pan, Xinhui" <Xinhui.Pan@....com>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        Daniel Vetter <daniel@...ll.ch>,
        "Deucher, Alexander" <Alexander.Deucher@....com>,
        "Koenig, Christian" <Christian.Koenig@....com>,
        "Zhang, Hawking" <Hawking.Zhang@....com>
Subject: RE: [PATCH v7 6/8] PCI/VGA: Introduce is_boot_device function
 callback to vga_client_register

[Public]

> -----Original Message-----
> From: 15330273260@....cn <15330273260@....cn>
> Sent: Thursday, June 29, 2023 12:00 PM
> To: Bjorn Helgaas <helgaas@...nel.org>; Sui Jingfeng
> <suijingfeng@...ngson.cn>
> Cc: Bjorn Helgaas <bhelgaas@...gle.com>; linux-fbdev@...r.kernel.org;
> Cornelia Huck <cohuck@...hat.com>; Karol Herbst <kherbst@...hat.com>;
> nouveau@...ts.freedesktop.org; Joonas Lahtinen
> <joonas.lahtinen@...ux.intel.com>; dri-devel@...ts.freedesktop.org; Chai,
> Thomas <YiPeng.Chai@....com>; Limonciello, Mario
> <Mario.Limonciello@....com>; Gao, Likun <Likun.Gao@....com>; David
> Airlie <airlied@...il.com>; Ville Syrjala <ville.syrjala@...ux.intel.com>; Yi Liu
> <yi.l.liu@...el.com>; kvm@...r.kernel.org; amd-gfx@...ts.freedesktop.org;
> Jason Gunthorpe <jgg@...pe.ca>; Ben Skeggs <bskeggs@...hat.com>; linux-
> pci@...r.kernel.org; Kevin Tian <kevin.tian@...el.com>; Lazar, Lijo
> <Lijo.Lazar@....com>; Thomas Zimmermann <tzimmermann@...e.de>;
> Zhang, Bokun <Bokun.Zhang@....com>; intel-gfx@...ts.freedesktop.org;
> Maarten Lankhorst <maarten.lankhorst@...ux.intel.com>; Jani Nikula
> <jani.nikula@...ux.intel.com>; Alex Williamson
> <alex.williamson@...hat.com>; Abhishek Sahu <abhsahu@...dia.com>;
> Maxime Ripard <mripard@...nel.org>; Rodrigo Vivi <rodrigo.vivi@...el.com>;
> Tvrtko Ursulin <tvrtko.ursulin@...ux.intel.com>; Yishai Hadas
> <yishaih@...dia.com>; Pan, Xinhui <Xinhui.Pan@....com>; linux-
> kernel@...r.kernel.org; Daniel Vetter <daniel@...ll.ch>; Deucher, Alexander
> <Alexander.Deucher@....com>; Koenig, Christian
> <Christian.Koenig@....com>; Zhang, Hawking <Hawking.Zhang@....com>
> Subject: Re: [PATCH v7 6/8] PCI/VGA: Introduce is_boot_device function
> callback to vga_client_register
>
> Hi,
>
> On 2023/6/29 23:54, Bjorn Helgaas wrote:
> > On Thu, Jun 22, 2023 at 01:08:15PM +0800, Sui Jingfeng wrote:
> >> Hi,
> >>
> >>
> >> A nouveau developer(Lyude) from redhat send me a R-B,
> >>
> >> Thanks for the developers of nouveau project.
> >>
> >>
> >> Please allow me add a link[1] here.
> >>
> >>
> >> [1]
> https://lore.kernel.org/all/0afadc69f99a36bc9d03ecf54ff25859dbc10e28.ca
> mel@...hat.com/
> > 1) Thanks for this.  If you post another version of this series,
> >     please pick up Lyude's Reviewed-by and include it in the relevant
> >     patches (as long as you haven't made significant changes to the
> >     code Lyude reviewed).
>
> Yes, no significant changes. Just fix typo.
>
> I also would like to add support for other DRM drivers.
>
> But I think this deserve another patch.
>
> >   Whoever applies this should automatically
> >     pick up Reviewed-by/Ack/etc that are replies to the version being
> >     applied, but they won't go through previous revisions to find them.
> >
> > 2) Please mention the commit to which the series applies.  I tried to
> >     apply this on v6.4-rc1, but it doesn't apply cleanly.
>
> Since I'm a graphic driver developer, I'm using drm-tip.
>
> I just have already pulled, it still apply cleanly on drm-tip.
>
> > 3) Thanks for including cover letters in your postings.  Please
> >     include a little changelog in the cover letter so we know what
> >     changed between v6 and v7, etc.
>
> No change between v6 and v7,
>
> it seems that it is because the mailbox don't allow me to sending too
> many mails a day.
>
> so some of the patch is failed to delivery because out of quota.
>
>
> > 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.
>
> I'm wondering
>
> 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?
>
> Emm, I don't know because my patch seems across different subsystem of
> Linux kernel.
>
> There is also a developer for AMDGPU (Mario) give me a R-B for the
> patch-0002 of this series.
>
> So, at least, PATCH-0001, PATCH-0002, PATCH-0003, PATCH-0004, PATCH-
> 0006
> are already OK(got reviewed by).
>
> Those 5 patch are already qualified to be merged, I think.

I think what you can do is pick up all the tags in your next version.  Once the
whole series has tags we can discuss how it merges.

>
> I means that if you could merge those 5 patch first, then there no need
> to send another version again.
>
> I will refine the rest patch with more details and description.
>
> I'm fear of making too much noise.
>
> > Bjorn

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ