From: Clemens Ladisch <clemens@ladisch.de>
To: Mike Frysinger <vapier@gentoo.org>
Cc: Lars-Peter Clausen <lars@metafoo.de>,
Tony Luck <tony.luck@intel.com>,
Fenghua Yu <fenghua.yu@intel.com>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
x86@kernel.org, linux-kernel@vger.kernel.org,
linux-ia64@vger.kernel.org,
uclinux-dist-devel@blackfin.uclinux.org,
Mark Brown <broonie@opensource.wolfsonmicro.com>
Subject: Re: [PATCH] firmware: Make firmware drivers generally available
Date: Fri, 17 Jun 2011 18:11:58 +0000 [thread overview]
Message-ID: <4DFB98EE.9000609@ladisch.de> (raw)
In-Reply-To: <BANLkTimWfT_LSLX36oLcSSYNqi4buBiJUQ@mail.gmail.com>
Mike Frysinger wrote:
> On Fri, Jun 17, 2011 at 09:16, Clemens Ladisch wrote:
> > It looks as if sigma.c doesn't actually belong into drivers/firmware.
> > That directory is for code that lets the kernel access the firmware
> > of the platform that the kernel itself runs on.
>
> -EMISSINGBETTERSUGGESTION
I *knew* somebody would ask. :)
"drivers/firmware" is the obvious name for both, but that makes
it ambiguous. I'd suggest to split the two subsystems into
"drivers/host-firmware" and "drivers/device-firmware".
Regards,
Clemens
WARNING: multiple messages have this Message-ID (diff)
From: Clemens Ladisch <clemens@ladisch.de>
To: Mike Frysinger <vapier@gentoo.org>
Cc: Lars-Peter Clausen <lars@metafoo.de>,
Tony Luck <tony.luck@intel.com>,
Fenghua Yu <fenghua.yu@intel.com>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
x86@kernel.org, linux-kernel@vger.kernel.org,
linux-ia64@vger.kernel.org,
uclinux-dist-devel@blackfin.uclinux.org,
Mark Brown <broonie@opensource.wolfsonmicro.com>
Subject: Re: [PATCH] firmware: Make firmware drivers generally available
Date: Fri, 17 Jun 2011 20:11:58 +0200 [thread overview]
Message-ID: <4DFB98EE.9000609@ladisch.de> (raw)
In-Reply-To: <BANLkTimWfT_LSLX36oLcSSYNqi4buBiJUQ@mail.gmail.com>
Mike Frysinger wrote:
> On Fri, Jun 17, 2011 at 09:16, Clemens Ladisch wrote:
> > It looks as if sigma.c doesn't actually belong into drivers/firmware.
> > That directory is for code that lets the kernel access the firmware
> > of the platform that the kernel itself runs on.
>
> -EMISSINGBETTERSUGGESTION
I *knew* somebody would ask. :)
"drivers/firmware" is the obvious name for both, but that makes
it ambiguous. I'd suggest to split the two subsystems into
"drivers/host-firmware" and "drivers/device-firmware".
Regards,
Clemens
next prev parent reply other threads:[~2011-06-17 18:11 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-17 10:24 [PATCH 1/2] ASoC: Fix ADAU1701 build in SND_SOC_ALL_CODECS Mark Brown
2011-06-17 10:24 ` [PATCH 2/2] ASoC: Add adau* drivers to the Analog Devices file patterns Mark Brown
2011-06-17 15:16 ` [Device-drivers-devel] " Mike Frysinger
2011-06-18 14:30 ` Mark Brown
2011-06-17 15:48 ` Liam Girdwood
2011-06-17 10:32 ` [PATCH 1/2] ASoC: Fix ADAU1701 build in SND_SOC_ALL_CODECS Mark Brown
2011-06-17 11:40 ` [PATCH] firmware: Make firmware drivers generally available Lars-Peter Clausen
2011-06-17 11:40 ` Lars-Peter Clausen
2011-06-17 13:16 ` Clemens Ladisch
2011-06-17 13:16 ` Clemens Ladisch
2011-06-17 15:56 ` Mike Frysinger
2011-06-17 15:56 ` Mike Frysinger
2011-06-17 18:11 ` Clemens Ladisch [this message]
2011-06-17 18:11 ` Clemens Ladisch
2011-06-17 18:25 ` Mike Frysinger
2011-06-17 18:25 ` Mike Frysinger
2011-06-21 0:35 ` Mark Brown
2011-06-21 0:35 ` Mark Brown
2011-06-21 1:45 ` [uclinux-dist-devel] [PATCH] firmware: Make firmware drivers Mike Frysinger
2011-06-21 1:45 ` [uclinux-dist-devel] [PATCH] firmware: Make firmware drivers generally available Mike Frysinger
2011-06-17 15:56 ` Mike Frysinger
2011-06-17 15:56 ` Mike Frysinger
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=4DFB98EE.9000609@ladisch.de \
--to=clemens@ladisch.de \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=fenghua.yu@intel.com \
--cc=hpa@zytor.com \
--cc=lars@metafoo.de \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=tony.luck@intel.com \
--cc=uclinux-dist-devel@blackfin.uclinux.org \
--cc=vapier@gentoo.org \
--cc=x86@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.