From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: "Barnabás Pőcze" <pobrn@protonmail.com>
Cc: linux-kernel@vger.kernel.org,
platform-driver-x86@vger.kernel.org,
Mark Gross <markgross@kernel.org>,
Hans de Goede <hdegoede@redhat.com>, Armin Wolf <W_Armin@gmx.de>
Subject: Re: [RFC PATCH v1] platform/x86: wmi: Do not register driver with invalid GUID
Date: Fri, 21 Jul 2023 12:17:22 +0300 [thread overview]
Message-ID: <ZLpNIsLrrQGWOQc/@smile.fi.intel.com> (raw)
In-Reply-To: <_szgAop-lIsQt90xoCYXQbiJtrQclFitfhE2ak2omTiPCx37toqB4lq7OTmBD_vMEn6TonpAns5NgVH1xFpGQLyuLkd0pOGwRqrB8C9INRw=@protonmail.com>
On Thu, Jul 20, 2023 at 10:42:29AM +0000, Barnabás Pőcze wrote:
> 2023. július 20., csütörtök 10:36 keltezéssel, Andy Shevchenko írta:
> > On Wed, Jul 19, 2023 at 07:23:37PM +0000, Barnabás Pőcze wrote:
...
> > Yes, that's what file2alias is for. We trust modules we build, right?
> > If you don't trust, then we have much bigger problem than this patch
> > tries to address.
> It seems we have to agree to disagree then.
I am confused. The parts are related to each other, you can't disagree on both.
You mean we have much bigger problem in the kernel or file2alias is the proper
place? I.o.w. which part you agree with and respectively disagree?
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2023-07-21 9:17 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-15 21:24 Barnabás Pőcze
2023-07-17 9:49 ` Andy Shevchenko
2023-07-17 11:23 ` Barnabás Pőcze
2023-07-17 11:31 ` Andy Shevchenko
2023-07-19 19:23 ` Barnabás Pőcze
2023-07-20 8:36 ` Andy Shevchenko
2023-07-20 10:42 ` Barnabás Pőcze
2023-07-21 9:17 ` Andy Shevchenko [this message]
2023-07-26 8:45 ` Hans de Goede
2023-07-27 22:54 ` Barnabás Pőcze
2023-07-28 10:02 ` Andy Shevchenko
2023-07-28 14:39 ` Barnabás Pőcze
2023-07-31 19:52 ` Andy Shevchenko
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=ZLpNIsLrrQGWOQc/@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=W_Armin@gmx.de \
--cc=hdegoede@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=markgross@kernel.org \
--cc=platform-driver-x86@vger.kernel.org \
--cc=pobrn@protonmail.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
Powered by JetHome