From: Sui Jingfeng <15330273260@189.cn>
To: Bjorn Helgaas <helgaas@kernel.org>,
Sui Jingfeng <suijingfeng@loongson.cn>
Cc: Bjorn Helgaas <bhelgaas@google.com>,
linux-fbdev@vger.kernel.org, Cornelia Huck <cohuck@redhat.com>,
Karol Herbst <kherbst@redhat.com>,
nouveau@lists.freedesktop.org,
Joonas Lahtinen <joonas.lahtinen@linux.intel.com>,
dri-devel@lists.freedesktop.org,
YiPeng Chai <YiPeng.Chai@amd.com>,
Mario Limonciello <mario.limonciello@amd.com>,
Likun Gao <Likun.Gao@amd.com>, David Airlie <airlied@gmail.com>,
Ville Syrjala <ville.syrjala@linux.intel.com>,
Yi Liu <yi.l.liu@intel.com>,
kvm@vger.kernel.org, amd-gfx@lists.freedesktop.org,
Jason Gunthorpe <jgg@ziepe.ca>, Ben Skeggs <bskeggs@redhat.com>,
linux-pci@vger.kernel.org, Kevin Tian <kevin.tian@intel.com>,
Lijo Lazar <lijo.lazar@amd.com>,
Thomas Zimmermann <tzimmermann@suse.de>,
Bokun Zhang <Bokun.Zhang@amd.com>,
intel-gfx@lists.freedesktop.org,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Jani Nikula <jani.nikula@linux.intel.com>,
Alex Williamson <alex.williamson@redhat.com>,
Abhishek Sahu <abhsahu@nvidia.com>,
Maxime Ripard <mripard@kernel.org>,
Rodrigo Vivi <rodrigo.vivi@intel.com>,
Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>,
Yishai Hadas <yishaih@nvidia.com>,
Pan Xinhui <Xinhui.Pan@amd.com>,
linux-kernel@vger.kernel.org, Daniel Vetter <daniel@ffwll.ch>,
Alex Deucher <alexander.deucher@amd.com>,
Christian Konig <christian.koenig@amd.com>,
Hawking Zhang <Hawking.Zhang@amd.com>
Subject: Re: [PATCH v7 6/8] PCI/VGA: Introduce is_boot_device function callback to vga_client_register
Date: Fri, 30 Jun 2023 01:00:10 +0800 [thread overview]
Message-ID: <bcfdc77d-a94d-bca1-56e3-5e14e91f6fd9@189.cn> (raw)
In-Reply-To: <20230629155436.GA397963@bhelgaas>
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.camel@redhat.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 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
next prev parent reply other threads:[~2023-06-29 17:00 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-13 3:01 [PATCH v7 0/8] PCI/VGA: Introduce is_boot_device function callback to vga_client_register Sui Jingfeng
2023-06-13 3:01 ` [PATCH v7 1/8] PCI/VGA: Use unsigned type for the io_state variable Sui Jingfeng
2023-06-13 3:01 ` [PATCH v7 2/8] PCI/VGA: Deal only with VGA class devices Sui Jingfeng
2023-06-14 10:50 ` Sui Jingfeng
2023-06-15 21:11 ` Alex Deucher
2023-06-16 7:11 ` Sui Jingfeng
2023-06-16 13:41 ` Alex Deucher
2023-06-16 14:22 ` Sui Jingfeng
2023-06-16 14:34 ` Alex Deucher
2023-06-16 15:44 ` Sui Jingfeng
2023-06-18 12:11 ` Sui Jingfeng
2023-06-19 2:17 ` Sui Jingfeng
2023-06-19 2:23 ` Sui Jingfeng
2023-06-21 7:33 ` Sui Jingfeng
2023-07-03 17:18 ` Sui Jingfeng
2023-06-19 3:02 ` Maciej W. Rozycki
2023-06-19 3:45 ` Sui Jingfeng
2023-06-13 3:01 ` [PATCH v7 3/8] PCI/VGA: Tidy up the code and comment format Sui Jingfeng
2023-06-13 3:01 ` [PATCH v7 4/8] PCI/VGA: Replace full MIT license text with SPDX identifier Sui Jingfeng
2023-06-13 3:01 ` [PATCH v7 5/8] video/aperture: Add a helper to detect if an aperture contains firmware FB Sui Jingfeng
2023-06-27 14:21 ` Sui Jingfeng
2023-06-13 3:01 ` [PATCH v7 6/8] PCI/VGA: Introduce is_boot_device function callback to vga_client_register Sui Jingfeng
2023-06-22 5:08 ` Sui Jingfeng
2023-06-29 15:54 ` Bjorn Helgaas
2023-06-29 17:00 ` Sui Jingfeng [this message]
2023-06-29 17:44 ` Limonciello, Mario
2023-06-30 2:14 ` suijingfeng
2023-06-30 17:41 ` Bjorn Helgaas
2023-06-30 18:32 ` Jani Nikula
2023-06-30 4:42 ` Sui Jingfeng
2023-06-27 14:35 ` Sui Jingfeng
2023-06-29 14:41 ` Sui Jingfeng
2023-06-13 3:01 ` [PATCH v7 7/8] drm/amdgpu: Implement the is_boot_device callback function Sui Jingfeng
2023-06-15 6:51 ` Sui Jingfeng
2023-06-13 3:01 ` [PATCH v7 8/8] drm/radeon: " Sui Jingfeng
2023-06-27 14:20 ` Sui Jingfeng
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=bcfdc77d-a94d-bca1-56e3-5e14e91f6fd9@189.cn \
--to=15330273260@189.cn \
--cc=Bokun.Zhang@amd.com \
--cc=Hawking.Zhang@amd.com \
--cc=Likun.Gao@amd.com \
--cc=Xinhui.Pan@amd.com \
--cc=YiPeng.Chai@amd.com \
--cc=abhsahu@nvidia.com \
--cc=airlied@gmail.com \
--cc=alex.williamson@redhat.com \
--cc=alexander.deucher@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=bhelgaas@google.com \
--cc=bskeggs@redhat.com \
--cc=christian.koenig@amd.com \
--cc=cohuck@redhat.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=helgaas@kernel.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=jgg@ziepe.ca \
--cc=joonas.lahtinen@linux.intel.com \
--cc=kevin.tian@intel.com \
--cc=kherbst@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=lijo.lazar@amd.com \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mario.limonciello@amd.com \
--cc=mripard@kernel.org \
--cc=nouveau@lists.freedesktop.org \
--cc=rodrigo.vivi@intel.com \
--cc=suijingfeng@loongson.cn \
--cc=tvrtko.ursulin@linux.intel.com \
--cc=tzimmermann@suse.de \
--cc=ville.syrjala@linux.intel.com \
--cc=yi.l.liu@intel.com \
--cc=yishaih@nvidia.com \
/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;
as well as URLs for NNTP newsgroup(s).