| /openbmc/linux/arch/powerpc/configs/85xx/ |
| H A D | ppa8548_defconfig | diff a85cade6762bf566698e625ec1a4461245e40768 Tue Jan 20 00:36:53 CST 2015 Michael Ellerman <mpe@ellerman.id.au> powerpc: Update all configs using savedefconfig
It looks like it's ~4 years since we updated some of these, so do a bulk
update.
Verified that the before and after generated configs are exactly the
same.
Which begs the question why update them? The answer is that it can be
confusing when the stored defconfig drifts too far from the generated
result.
Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
|
| H A D | ge_imp3a_defconfig | diff a85cade6762bf566698e625ec1a4461245e40768 Tue Jan 20 00:36:53 CST 2015 Michael Ellerman <mpe@ellerman.id.au> powerpc: Update all configs using savedefconfig
It looks like it's ~4 years since we updated some of these, so do a bulk
update.
Verified that the before and after generated configs are exactly the
same.
Which begs the question why update them? The answer is that it can be
confusing when the stored defconfig drifts too far from the generated
result.
Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
|
| H A D | socrates_defconfig | diff a85cade6762bf566698e625ec1a4461245e40768 Tue Jan 20 00:36:53 CST 2015 Michael Ellerman <mpe@ellerman.id.au> powerpc: Update all configs using savedefconfig
It looks like it's ~4 years since we updated some of these, so do a bulk
update.
Verified that the before and after generated configs are exactly the
same.
Which begs the question why update them? The answer is that it can be
confusing when the stored defconfig drifts too far from the generated
result.
Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
|
| /openbmc/linux/arch/powerpc/configs/44x/ |
| H A D | bluestone_defconfig | diff a85cade6762bf566698e625ec1a4461245e40768 Tue Jan 20 00:36:53 CST 2015 Michael Ellerman <mpe@ellerman.id.au> powerpc: Update all configs using savedefconfig
It looks like it's ~4 years since we updated some of these, so do a bulk
update.
Verified that the before and after generated configs are exactly the
same.
Which begs the question why update them? The answer is that it can be
confusing when the stored defconfig drifts too far from the generated
result.
Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
|
| H A D | currituck_defconfig | diff a85cade6762bf566698e625ec1a4461245e40768 Tue Jan 20 00:36:53 CST 2015 Michael Ellerman <mpe@ellerman.id.au> powerpc: Update all configs using savedefconfig
It looks like it's ~4 years since we updated some of these, so do a bulk
update.
Verified that the before and after generated configs are exactly the
same.
Which begs the question why update them? The answer is that it can be
confusing when the stored defconfig drifts too far from the generated
result.
Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
|
| H A D | akebono_defconfig | diff a85cade6762bf566698e625ec1a4461245e40768 Tue Jan 20 00:36:53 CST 2015 Michael Ellerman <mpe@ellerman.id.au> powerpc: Update all configs using savedefconfig
It looks like it's ~4 years since we updated some of these, so do a bulk
update.
Verified that the before and after generated configs are exactly the
same.
Which begs the question why update them? The answer is that it can be
confusing when the stored defconfig drifts too far from the generated
result.
Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
|
| H A D | icon_defconfig | diff a85cade6762bf566698e625ec1a4461245e40768 Tue Jan 20 00:36:53 CST 2015 Michael Ellerman <mpe@ellerman.id.au> powerpc: Update all configs using savedefconfig
It looks like it's ~4 years since we updated some of these, so do a bulk
update.
Verified that the before and after generated configs are exactly the
same.
Which begs the question why update them? The answer is that it can be
confusing when the stored defconfig drifts too far from the generated
result.
Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
|
| H A D | eiger_defconfig | diff a85cade6762bf566698e625ec1a4461245e40768 Tue Jan 20 00:36:53 CST 2015 Michael Ellerman <mpe@ellerman.id.au> powerpc: Update all configs using savedefconfig
It looks like it's ~4 years since we updated some of these, so do a bulk
update.
Verified that the before and after generated configs are exactly the
same.
Which begs the question why update them? The answer is that it can be
confusing when the stored defconfig drifts too far from the generated
result.
Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
|
| H A D | iss476-smp_defconfig | diff a85cade6762bf566698e625ec1a4461245e40768 Tue Jan 20 00:36:53 CST 2015 Michael Ellerman <mpe@ellerman.id.au> powerpc: Update all configs using savedefconfig
It looks like it's ~4 years since we updated some of these, so do a bulk
update.
Verified that the before and after generated configs are exactly the
same.
Which begs the question why update them? The answer is that it can be
confusing when the stored defconfig drifts too far from the generated
result.
Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
|
| H A D | redwood_defconfig | diff a85cade6762bf566698e625ec1a4461245e40768 Tue Jan 20 00:36:53 CST 2015 Michael Ellerman <mpe@ellerman.id.au> powerpc: Update all configs using savedefconfig
It looks like it's ~4 years since we updated some of these, so do a bulk
update.
Verified that the before and after generated configs are exactly the
same.
Which begs the question why update them? The answer is that it can be
confusing when the stored defconfig drifts too far from the generated
result.
Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
|
| H A D | ebony_defconfig | diff a85cade6762bf566698e625ec1a4461245e40768 Tue Jan 20 00:36:53 CST 2015 Michael Ellerman <mpe@ellerman.id.au> powerpc: Update all configs using savedefconfig
It looks like it's ~4 years since we updated some of these, so do a bulk
update.
Verified that the before and after generated configs are exactly the
same.
Which begs the question why update them? The answer is that it can be
confusing when the stored defconfig drifts too far from the generated
result.
Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
|
| H A D | bamboo_defconfig | diff a85cade6762bf566698e625ec1a4461245e40768 Tue Jan 20 00:36:53 CST 2015 Michael Ellerman <mpe@ellerman.id.au> powerpc: Update all configs using savedefconfig
It looks like it's ~4 years since we updated some of these, so do a bulk
update.
Verified that the before and after generated configs are exactly the
same.
Which begs the question why update them? The answer is that it can be
confusing when the stored defconfig drifts too far from the generated
result.
Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
|
| H A D | arches_defconfig | diff a85cade6762bf566698e625ec1a4461245e40768 Tue Jan 20 00:36:53 CST 2015 Michael Ellerman <mpe@ellerman.id.au> powerpc: Update all configs using savedefconfig
It looks like it's ~4 years since we updated some of these, so do a bulk
update.
Verified that the before and after generated configs are exactly the
same.
Which begs the question why update them? The answer is that it can be
confusing when the stored defconfig drifts too far from the generated
result.
Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
|
| H A D | rainier_defconfig | diff a85cade6762bf566698e625ec1a4461245e40768 Tue Jan 20 00:36:53 CST 2015 Michael Ellerman <mpe@ellerman.id.au> powerpc: Update all configs using savedefconfig
It looks like it's ~4 years since we updated some of these, so do a bulk
update.
Verified that the before and after generated configs are exactly the
same.
Which begs the question why update them? The answer is that it can be
confusing when the stored defconfig drifts too far from the generated
result.
Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
|
| /openbmc/linux/arch/powerpc/configs/ |
| H A D | mvme5100_defconfig | diff a85cade6762bf566698e625ec1a4461245e40768 Tue Jan 20 00:36:53 CST 2015 Michael Ellerman <mpe@ellerman.id.au> powerpc: Update all configs using savedefconfig
It looks like it's ~4 years since we updated some of these, so do a bulk
update.
Verified that the before and after generated configs are exactly the
same.
Which begs the question why update them? The answer is that it can be
confusing when the stored defconfig drifts too far from the generated
result.
Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
|
| H A D | holly_defconfig | diff a85cade6762bf566698e625ec1a4461245e40768 Tue Jan 20 00:36:53 CST 2015 Michael Ellerman <mpe@ellerman.id.au> powerpc: Update all configs using savedefconfig
It looks like it's ~4 years since we updated some of these, so do a bulk
update.
Verified that the before and after generated configs are exactly the
same.
Which begs the question why update them? The answer is that it can be
confusing when the stored defconfig drifts too far from the generated
result.
Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
|
| H A D | amigaone_defconfig | diff a85cade6762bf566698e625ec1a4461245e40768 Tue Jan 20 00:36:53 CST 2015 Michael Ellerman <mpe@ellerman.id.au> powerpc: Update all configs using savedefconfig
It looks like it's ~4 years since we updated some of these, so do a bulk
update.
Verified that the before and after generated configs are exactly the
same.
Which begs the question why update them? The answer is that it can be
confusing when the stored defconfig drifts too far from the generated
result.
Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
|
| H A D | gamecube_defconfig | diff a85cade6762bf566698e625ec1a4461245e40768 Tue Jan 20 00:36:53 CST 2015 Michael Ellerman <mpe@ellerman.id.au> powerpc: Update all configs using savedefconfig
It looks like it's ~4 years since we updated some of these, so do a bulk
update.
Verified that the before and after generated configs are exactly the
same.
Which begs the question why update them? The answer is that it can be
confusing when the stored defconfig drifts too far from the generated
result.
Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
|
| H A D | tqm8xx_defconfig | diff a85cade6762bf566698e625ec1a4461245e40768 Tue Jan 20 00:36:53 CST 2015 Michael Ellerman <mpe@ellerman.id.au> powerpc: Update all configs using savedefconfig
It looks like it's ~4 years since we updated some of these, so do a bulk
update.
Verified that the before and after generated configs are exactly the
same.
Which begs the question why update them? The answer is that it can be
confusing when the stored defconfig drifts too far from the generated
result.
Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
|
| /openbmc/linux/arch/powerpc/configs/40x/ |
| H A D | obs600_defconfig | diff a85cade6762bf566698e625ec1a4461245e40768 Tue Jan 20 00:36:53 CST 2015 Michael Ellerman <mpe@ellerman.id.au> powerpc: Update all configs using savedefconfig
It looks like it's ~4 years since we updated some of these, so do a bulk
update.
Verified that the before and after generated configs are exactly the
same.
Which begs the question why update them? The answer is that it can be
confusing when the stored defconfig drifts too far from the generated
result.
Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
|
| H A D | klondike_defconfig | diff a85cade6762bf566698e625ec1a4461245e40768 Tue Jan 20 00:36:53 CST 2015 Michael Ellerman <mpe@ellerman.id.au> powerpc: Update all configs using savedefconfig
It looks like it's ~4 years since we updated some of these, so do a bulk
update.
Verified that the before and after generated configs are exactly the
same.
Which begs the question why update them? The answer is that it can be
confusing when the stored defconfig drifts too far from the generated
result.
Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
|
| H A D | walnut_defconfig | diff a85cade6762bf566698e625ec1a4461245e40768 Tue Jan 20 00:36:53 CST 2015 Michael Ellerman <mpe@ellerman.id.au> powerpc: Update all configs using savedefconfig
It looks like it's ~4 years since we updated some of these, so do a bulk
update.
Verified that the before and after generated configs are exactly the
same.
Which begs the question why update them? The answer is that it can be
confusing when the stored defconfig drifts too far from the generated
result.
Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
|
| H A D | makalu_defconfig | diff a85cade6762bf566698e625ec1a4461245e40768 Tue Jan 20 00:36:53 CST 2015 Michael Ellerman <mpe@ellerman.id.au> powerpc: Update all configs using savedefconfig
It looks like it's ~4 years since we updated some of these, so do a bulk
update.
Verified that the before and after generated configs are exactly the
same.
Which begs the question why update them? The answer is that it can be
confusing when the stored defconfig drifts too far from the generated
result.
Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
|
| H A D | acadia_defconfig | diff a85cade6762bf566698e625ec1a4461245e40768 Tue Jan 20 00:36:53 CST 2015 Michael Ellerman <mpe@ellerman.id.au> powerpc: Update all configs using savedefconfig
It looks like it's ~4 years since we updated some of these, so do a bulk
update.
Verified that the before and after generated configs are exactly the
same.
Which begs the question why update them? The answer is that it can be
confusing when the stored defconfig drifts too far from the generated
result.
Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
|
| /openbmc/linux/arch/powerpc/configs/83xx/ |
| H A D | kmeter1_defconfig | diff a85cade6762bf566698e625ec1a4461245e40768 Tue Jan 20 00:36:53 CST 2015 Michael Ellerman <mpe@ellerman.id.au> powerpc: Update all configs using savedefconfig
It looks like it's ~4 years since we updated some of these, so do a bulk
update.
Verified that the before and after generated configs are exactly the
same.
Which begs the question why update them? The answer is that it can be
confusing when the stored defconfig drifts too far from the generated
result.
Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
|