[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <1422407074.32234.2.camel@ellerman.id.au>
Date: Wed, 28 Jan 2015 12:04:34 +1100
From: Michael Ellerman <mpe@...erman.id.au>
To: semen.protsenko@...ballogic.com
Cc: Paul Bolle <pebolle@...cali.nl>, linux-mips@...ux-mips.org,
Brian Norris <computersforpeace@...il.com>,
Russell King <linux@....linux.org.uk>,
linux-sh@...r.kernel.org,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
linuxppc-dev@...ts.ozlabs.org,
Hans-Christian Egtvedt <egtvedt@...fundet.no>,
adi-buildroot-devel@...ts.sourceforge.net,
linux-kernel@...r.kernel.org, linux-m68k@...ts.linux-m68k.org,
linux-am33-list@...hat.com,
Geert Uytterhoeven <geert@...ux-m68k.org>,
Koichi Yasutake <yasutake.koichi@...panasonic.com>,
linux-mtd@...ts.infradead.org, Guan Xuetao <gxt@...c.pku.edu.cn>,
David Woodhouse <dwmw2@...radead.org>,
linux-arm-kernel@...ts.infradead.org,
Haavard Skinnemoen <hskinnemoen@...il.com>
Subject: Re: [PATCH 0/4] defconfigs: cleanup obsolete MTD configs
On Sat, 2015-01-24 at 22:54 +0200, Sam Protsenko wrote:
> > That's news for me. I thought they are silently ignored. Do you have an
> > example of such a warning?
>
> Not really. It was just assumption. It seems you are right, they are just
> ignored silently. But item 2 is still relevant and it was actually confused
> me when I tried to figure out MTD configuration for my platform.
> Anyway, garbage should be taken out from time to time.
The usual way that this gets dealt with is that arch maintainers (ir)regularly
run make savedefconfig on all their defconfigs.
As it happens we've done that on powerpc just recently, if you rebase onto next
you should see that, so you can drop the powerpc hunks from your patches.
cheers
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists