From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Kurt Borja <kuurtb@gmail.com>
Cc: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>,
platform-driver-x86@vger.kernel.org,
linux-kernel@vger.kernel.org,
"Hans de Goede" <hdegoede@redhat.com>,
"Mario Limonciello" <mario.limonciello@amd.com>,
"Prasanth Ksr" <prasanth.ksr@dell.com>,
Dell.Client.Kernel@dell.com
Subject: Re: [PATCH 1/4] platform/x86: dell: dell-wmi-sysman: Use *-y instead of *-objs in Makefile
Date: Wed, 19 Feb 2025 16:35:16 +0200 [thread overview]
Message-ID: <Z7XsJMwFhZLk-0S4@smile.fi.intel.com> (raw)
In-Reply-To: <20250218194113.26589-2-kuurtb@gmail.com>
On Tue, Feb 18, 2025 at 02:41:08PM -0500, Kurt Borja wrote:
> The `objs` suffix is reserved for user-space tools. Use the `y` suffix
> instead, which is usually used for kernel drivers.
I haven't received a cover letter. Please, make sure when you send a version of
the few patches under the same thread you add a cover letter. You may consider
using my "smart" (not really) script [1] to send patch series to LKML.
[1]: https://github.com/andy-shev/home-bin-tools/blob/master/ge2maintainer.sh
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2025-02-19 14:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-18 19:41 [PATCH 0/4] platform-x86: Use *-y instead of *-objs in Makefiles Kurt Borja
2025-02-18 19:41 ` [PATCH 1/4] platform/x86: dell: dell-wmi-sysman: Use *-y instead of *-objs in Makefile Kurt Borja
2025-02-19 14:35 ` Andy Shevchenko [this message]
2025-02-20 16:13 ` Kurt Borja
2025-02-18 19:41 ` [PATCH 2/4] platform/x86: amd: Use *-y instead of *-objs in Makefiles Kurt Borja
2025-02-18 19:41 ` [PATCH 3/4] platform/x86: hp: Use *-y instead of *-objs in Makefile Kurt Borja
2025-02-18 19:41 ` [PATCH 4/4] platform/x86: intel: " Kurt Borja
2025-02-19 0:10 ` Joseph, Jithu
2025-02-19 14:36 ` Andy Shevchenko
2025-02-24 15:17 ` [PATCH 0/4] platform-x86: Use *-y instead of *-objs in Makefiles Ilpo Järvinen
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=Z7XsJMwFhZLk-0S4@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=Dell.Client.Kernel@dell.com \
--cc=hdegoede@redhat.com \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=kuurtb@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mario.limonciello@amd.com \
--cc=platform-driver-x86@vger.kernel.org \
--cc=prasanth.ksr@dell.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