From: David Woodhouse <dwmw2@infradead.org>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-kernel@vger.kernel.org
Cc: linux-kbuild@vger.kernel.org, Kyle McMartin <kyle@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Michal Marek <mmarek@suse.com>,
Masahiro Yamada <yamada.masahiro@socionext.com>
Subject: Re: [PATCH] firmware: delete in-kernel firmware
Date: Thu, 14 Sep 2017 14:39:07 -0700 [thread overview]
Message-ID: <1505425147.29318.3.camel@infradead.org> (raw)
In-Reply-To: <20170914213339.GA3072@kroah.com>
[-- Attachment #1: Type: text/plain, Size: 1120 bytes --]
On Thu, 2017-09-14 at 14:33 -0700, Greg Kroah-Hartman wrote:
> The last firmware change for the in-kernel firmware source code was back
> in 2013. Everyone has been relying on the out-of-tree linux-firmware
> package for a long long time.
>
> So let's drop it, it's baggage we don't need to keep dragging around
> (and having to fix random kbuild issues over time...)
>
> Cc: David Woodhouse <dwmw2@infradead.org>
> Cc: Kyle McMartin <kyle@kernel.org>
> Cc: Andrew Morton <akpm@linux-foundation.org>
> Cc: Michal Marek <mmarek@suse.com>
> Cc: Masahiro Yamada <yamada.masahiro@socionext.com>
> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> ---
>
> This has gone on too long, let's just drop it for 4.14. Any objections?
Acked-by: David Woodhouse <dwmw2@infradead.org>
This has been the plan for a very long time, and we even agreed to do
it at the Kernel Summit in Boston. ISTR there was one final technical
thing we wanted to fix for the out-of-kernel tree which stopped me from
sending the patch that day, but that's long since irrelevant now. Let's
do it.
Thanks.
[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 4938 bytes --]
prev parent reply other threads:[~2017-09-14 22:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-14 21:33 [PATCH] firmware: delete in-kernel firmware Greg Kroah-Hartman
2017-09-14 21:39 ` David Woodhouse [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=1505425147.29318.3.camel@infradead.org \
--to=dwmw2@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=gregkh@linuxfoundation.org \
--cc=kyle@kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mmarek@suse.com \
--cc=yamada.masahiro@socionext.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;
as well as URLs for NNTP newsgroup(s).