public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Markus Trippelsdorf <markus@trippelsdorf.de>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	Kyle McMartin <kyle@kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Michal Marek <mmarek@suse.com>,
	Masahiro Yamada <yamada.masahiro@socionext.com>,
	David Woodhouse <dwmw2@infradead.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] firmware: Restore support for built-in firmware
Date: Sat, 16 Sep 2017 09:57:05 -0700	[thread overview]
Message-ID: <20170916165705.GB4577@kroah.com> (raw)
In-Reply-To: <20170916090116.GA1846@x4>

On Sat, Sep 16, 2017 at 11:01:16AM +0200, Markus Trippelsdorf wrote:
> Commit 5620a0d1aac ("firmware: delete in-kernel firmware") removed the
> entire firmware directory. Unfortunately it thereby also removed the
> support for built-in firmware.

The goal was to delete the in-kernel firmware, why do you want to add it
back?

> This restores the ability to build firmware directly into the kernel by
> pruning the original Makefile to the necessary minimum. The default for
> EXTRA_FIRMWARE_DIR is now the standard directory /lib/firmware/.

But what firmware is this fixing the build for?

As I asked in the other email, I don't understand the problem here, but
it's early, and the Plumbers closing party lasted really late...

thanks,

greg k-h

      reply	other threads:[~2017-09-16 16:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-16  9:01 [PATCH] firmware: Restore support for built-in firmware Markus Trippelsdorf
2017-09-16 16:57 ` Greg KH [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=20170916165705.GB4577@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=akpm@linux-foundation.org \
    --cc=dwmw2@infradead.org \
    --cc=kyle@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=markus@trippelsdorf.de \
    --cc=mmarek@suse.com \
    --cc=torvalds@linux-foundation.org \
    --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