All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Kurt Borja" <kuurtb@gmail.com>
To: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
Cc: "Hans de Goede" <hdegoede@redhat.com>,
	platform-driver-x86@vger.kernel.org,
	LKML <linux-kernel@vger.kernel.org>,
	"Pali Rohár" <pali@kernel.org>,
	Dell.Client.Kernel@dell.com,
	"Matthew Garrett" <mjg59@srcf.ucam.org>,
	"Andy Shevchenko" <andriy.shevchenko@linux.intel.com>
Subject: Re: [PATCH] platform/x86: dell: Use *-y instead of *-objs in Makefile
Date: Tue, 18 Feb 2025 14:09:56 -0500	[thread overview]
Message-ID: <D7VT4O9N3KD3.3DK9CY1TODOMR@gmail.com> (raw)
In-Reply-To: <cc0f1964-ae37-4cfb-b5d2-da2e2a97e522@linux.intel.com>

On Mon Feb 17, 2025 at 3:58 AM -05, Ilpo Järvinen wrote:
> On Fri, 14 Feb 2025, Kurt Borja wrote:
>
>> The `objs` suffix is reserved for user-space tools. Use the `y` suffix
>> instead, which is usually used for kernel drivers.
>> 
>> Suggested-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
>> Signed-off-by: Kurt Borja <kuurtb@gmail.com>
>> ---
>> Hi all,
>> 
>> I based this patch on top of the for-next branch.
>> 
>> Ilpo, if you prefer this patch to be based on top of the fixes branch,
>> let me know. I'd submit two separate patches, one for alienware-wmi, on
>> top of the for-next branch and one for the other drivers, on top of
>> fixes.
>
> Thanks for the fix.
>
> I took this through for-next branch to not make our lives unnecessarily 
> complicated. If there would be only handful of -objs, I might have decide 
> otherwise but this (wrong) pattern is really widespread so removing a few 
> drops from the ocean is not going to sound us the finish line fanfare. But 
> it's still an important step towards the right direction, regardless.
>
> TBH, I didn't know the distinction either until Andy explained it (and 
> like you, would have just copied the pattern if one was readily 
> available). But I've never really deep dived into the kernel's build 
> system anyway.

I will finish the job for this subsystem, so no one copies this pattern
again :p

>
> I wonder why checkpatch doesn't catch it, or does it? At least there are 
> no "objs" strings in its source.

It doesn't actually. Not even with --strict.

-- 
 ~ Kurt

      reply	other threads:[~2025-02-18 19:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-14 21:45 [PATCH] platform/x86: dell: Use *-y instead of *-objs in Makefile Kurt Borja
2025-02-16 20:24 ` Andy Shevchenko
2025-02-17  8:58 ` Ilpo Järvinen
2025-02-18 19:09   ` Kurt Borja [this message]

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=D7VT4O9N3KD3.3DK9CY1TODOMR@gmail.com \
    --to=kuurtb@gmail.com \
    --cc=Dell.Client.Kernel@dell.com \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=hdegoede@redhat.com \
    --cc=ilpo.jarvinen@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mjg59@srcf.ucam.org \
    --cc=pali@kernel.org \
    --cc=platform-driver-x86@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.