Dave, do you have a preference how to deal with the mishap here, shall I do a
force-push to drm-intel-gt-next to correctly record the Acked-by or revert and
re-push? Or just leave it as is?
Quoting Greg Kroah-Hartman (2022-09-01 18:09:09)
On Sat, Aug 06, 2022 at 03:26:21PM +0300, Tomas Winkler wrote:Daniele, why were the patches applied without this A-b?
Add GSC support for XeHP SDV and DG2 platforms.With the exception that you all don't know what year it is:
The series includes changes for the mei driver:
- add ability to use polling instead of interrupts
- add ability to use extended timeouts
- setup extended operational memory for GSC
The series includes changes for the i915 driver:
- allocate extended operational memory for GSC
- GSC on XeHP SDV offsets and definitions
This patch set should be merged via gfx tree as
the auxiliary device belongs there.
Greg, your ACK is required for the drives/misc/mei code base,
please review the patches.
Acked-by: Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx>
I'm just preparing the drm-intel-gt-next pull request and now it appears
like we're pushing a lot of commits outside of drm without any Acks.
Please reach out to the maintainers *before* pushing code for other
subsystems. Unless you get an explicit ack to do so, do not push such
code.
Quoting from the committer guidelines[1] the first rule is:
"Only push patches changing drivers/gpu/drm/i915."
In those cases, please ping a maintainer and don't rush things.
Regards, Joonas
[1] https://drm.pages.freedesktop.org/maintainer-tools/committer-drm-intel.html#high-level-guidelines