From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: Linus Walleij <linus.walleij@linaro.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Re: [PATCH v1 1/1] usb: fotg210: Use *-y instead of *-objs in Makefile
Date: Wed, 8 May 2024 18:06:50 +0300 [thread overview]
Message-ID: <ZjuVCvQw4aL0x42W@smile.fi.intel.com> (raw)
In-Reply-To: <20240508150406.1378672-1-andriy.shevchenko@linux.intel.com>
On Wed, May 08, 2024 at 06:04:06PM +0300, Andy Shevchenko wrote:
> *-objs suffix is reserved rather for (user-space) host programs while
> usually *-y suffix is used for kernel drivers (although *-objs works
> for that purpose for now).
>
> Let's correct the old usages of *-objs in Makefiles.
Note, the original approach is weirdest from existing. Only a few
drivers use this (-objs-y) one most likely by mistake.
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2024-05-08 15:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-08 15:04 [PATCH v1 1/1] usb: fotg210: Use *-y instead of *-objs in Makefile Andy Shevchenko
2024-05-08 15:06 ` Andy Shevchenko [this message]
2024-05-27 13:18 ` Linus Walleij
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=ZjuVCvQw4aL0x42W@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox