From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Alexander Usyskin <alexander.usyskin@intel.com>
Cc: Lucas De Marchi <lucas.demarchi@intel.com>,
Daniele Ceraolo Spurio <daniele.ceraolospurio@intel.com>,
Rodrigo Vivi <rodrigo.vivi@intel.com>,
Tomas Winkler <tomas.winkler@intel.com>,
Vitaly Lubart <vitaly.lubart@intel.com>,
intel-xe@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/5] Revert "mei/hdcp: Also enable for XE"
Date: Tue, 14 Nov 2023 07:12:50 -0500 [thread overview]
Message-ID: <2023111451-campsite-eaten-b8e3@gregkh> (raw)
In-Reply-To: <20231114100843.1923977-2-alexander.usyskin@intel.com>
On Tue, Nov 14, 2023 at 12:08:39PM +0200, Alexander Usyskin wrote:
> This reverts commit 62db7d00efe48c614b006086f306d5addedf8f83.
>
> It will be replaced by match without driver name.
Again, you are saying _what_ you are doing, but not _why_ you are doing
this. I have no clue why this current matching is not acceptable.
And did you just break the existing code if only this patch is applied?
> Signed-off-by: Alexander Usyskin <alexander.usyskin@intel.com>
As I asked this same question last review cycle, I'm now going to be
very picky and say "You are not following the documented Intel procedure
for Linux kernel patches that Greg has to review." Please work with
your internal Intel kernel developers to fix this, otherwise we can not
take them at all, sorry.
thanks,
greg k-h
next prev parent reply other threads:[~2023-11-14 12:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-14 10:08 [PATCH v2 0/5] mei: hdcp/pxp: adapt for Xe driver Alexander Usyskin
2023-11-14 10:08 ` [PATCH v2 1/5] Revert "mei/hdcp: Also enable for XE" Alexander Usyskin
2023-11-14 12:12 ` Greg Kroah-Hartman [this message]
2023-11-14 10:08 ` [PATCH v2 2/5] mei: hdcp: match without driver name Alexander Usyskin
2023-11-14 10:08 ` [PATCH v2 3/5] mei: pxp: " Alexander Usyskin
2023-11-14 10:08 ` [PATCH v2 4/5] mei: hdcp: add dependency on Xe driver Alexander Usyskin
2023-11-14 10:08 ` [PATCH v2 5/5] mei: pxp: " Alexander Usyskin
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=2023111451-campsite-eaten-b8e3@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=alexander.usyskin@intel.com \
--cc=daniele.ceraolospurio@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lucas.demarchi@intel.com \
--cc=rodrigo.vivi@intel.com \
--cc=tomas.winkler@intel.com \
--cc=vitaly.lubart@intel.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
all inboxes | Powered by JetHome®