From: "Arnd Bergmann" <arnd@arndb.de>
To: "Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Thorsten Leemhuis" <linux@leemhuis.info>
Cc: "Philipp Hortmann" <philipp.g.hortmann@gmail.com>,
linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org,
"Kalle Valo" <kvalo@kernel.org>,
"Larry Finger" <Larry.Finger@lwfinger.net>,
linux-next <linux-next@vger.kernel.org>
Subject: Re: [PATCH v2] staging: rtl8192u: Remove broken driver
Date: Tue, 17 Oct 2023 09:44:38 +0200 [thread overview]
Message-ID: <6d362e80-9837-4dab-99a5-51b8eb241b5b@app.fastmail.com> (raw)
In-Reply-To: <2023101752-canteen-uniformly-acc1@gregkh>
On Tue, Oct 17, 2023, at 09:20, Greg Kroah-Hartman wrote:
> On Tue, Oct 17, 2023 at 07:33:49AM +0200, Thorsten Leemhuis wrote:
>> On 14.10.23 23:10, Philipp Hortmann wrote:
next-next-all/builder-live.log.gz
>>
>> Made me wonder if this patch left something behind; a quick grep showed
>> something suspicious in drivers/staging/Makefile:
>> """
>> obj-$(CONFIG_RTL8192U) += rtl8192u/
>> """
>
> If you did 'make oldconfig' the option should have been removed and then
> this line wouldn't have triggered, right? Odd, but I'll go drop this
> entry as well.
It looks like "make clean" enters both the obj-y and obj-n directories,
unlike 'make vmlinux' or 'make modules', which only care about
obj-m and obj-y.
Arnd
prev parent reply other threads:[~2023-10-17 7:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-14 21:10 [PATCH v2] staging: rtl8192u: Remove broken driver Philipp Hortmann
2023-10-17 5:33 ` Thorsten Leemhuis
2023-10-17 7:20 ` Greg Kroah-Hartman
2023-10-17 7:42 ` Thorsten Leemhuis
2023-10-17 7:44 ` Arnd Bergmann [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=6d362e80-9837-4dab-99a5-51b8eb241b5b@app.fastmail.com \
--to=arnd@arndb.de \
--cc=Larry.Finger@lwfinger.net \
--cc=gregkh@linuxfoundation.org \
--cc=kvalo@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=linux@leemhuis.info \
--cc=philipp.g.hortmann@gmail.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