Home
last modified time | relevance | path

Searched hist:a1d9a09a (Results 1 – 2 of 2) sorted by relevance

/openbmc/linux/drivers/firmware/google/
H A DKconfiga1d9a09a Fri Apr 29 19:39:31 CDT 2011 Mike Waychison <mikew@google.com> Introduce CONFIG_GOOGLE_FIRMWARE

In order to keep Google's firmware drivers organized amongst themselves,
all Google firmware drivers are gated on CONFIG_GOOGLE_FIRMWARE=y, which
defaults to 'n' in the kernel build.

Signed-off-by: Mike Waychison <mikew@google.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
a1d9a09a Fri Apr 29 19:39:31 CDT 2011 Mike Waychison <mikew@google.com> Introduce CONFIG_GOOGLE_FIRMWARE

In order to keep Google's firmware drivers organized amongst themselves,
all Google firmware drivers are gated on CONFIG_GOOGLE_FIRMWARE=y, which
defaults to 'n' in the kernel build.

Signed-off-by: Mike Waychison <mikew@google.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
/openbmc/linux/drivers/firmware/
H A DMakefilea1d9a09a Fri Apr 29 19:39:31 CDT 2011 Mike Waychison <mikew@google.com> Introduce CONFIG_GOOGLE_FIRMWARE

In order to keep Google's firmware drivers organized amongst themselves,
all Google firmware drivers are gated on CONFIG_GOOGLE_FIRMWARE=y, which
defaults to 'n' in the kernel build.

Signed-off-by: Mike Waychison <mikew@google.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
a1d9a09a Fri Apr 29 19:39:31 CDT 2011 Mike Waychison <mikew@google.com> Introduce CONFIG_GOOGLE_FIRMWARE

In order to keep Google's firmware drivers organized amongst themselves,
all Google firmware drivers are gated on CONFIG_GOOGLE_FIRMWARE=y, which
defaults to 'n' in the kernel build.

Signed-off-by: Mike Waychison <mikew@google.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>