Linux-mtd Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Ellerman <mpe@ellerman.id.au>
To: semen.protsenko@globallogic.com
Cc: linux-mips@linux-mips.org, Paul Bolle <pebolle@tiscali.nl>,
	linux-am33-list@redhat.com, Russell King <linux@arm.linux.org.uk>,
	linux-sh@vger.kernel.org,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	adi-buildroot-devel@lists.sourceforge.net,
	linux-kernel@vger.kernel.org,
	Haavard Skinnemoen <hskinnemoen@gmail.com>,
	linux-m68k@lists.linux-m68k.org,
	Geert Uytterhoeven <geert@linux-m68k.org>,
	Koichi Yasutake <yasutake.koichi@jp.panasonic.com>,
	Guan Xuetao <gxt@mprc.pku.edu.cn>,
	linux-mtd@lists.infradead.org,
	Brian Norris <computersforpeace@gmail.com>,
	linuxppc-dev@lists.ozlabs.org,
	David Woodhouse <dwmw2@infradead.org>,
	linux-arm-kernel@lists.infradead.org,
	Hans-Christian Egtvedt <egtvedt@samfundet.no>
Subject: Re: [PATCH 0/4] defconfigs: cleanup obsolete MTD configs
Date: Wed, 28 Jan 2015 12:04:34 +1100	[thread overview]
Message-ID: <1422407074.32234.2.camel@ellerman.id.au> (raw)
In-Reply-To: <CAJOTznWHpRh8ysVxwSWyvZL1UAe-G9A64j=M6z0+zPeoycgkDg@mail.gmail.com>

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

  reply	other threads:[~2015-01-28  1:04 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-24 16:33 [PATCH 0/4] defconfigs: cleanup obsolete MTD configs Semen Protsenko
2015-01-24 16:33 ` [PATCH 1/4] defconfigs: remove CONFIG_MTD_CONCAT Semen Protsenko
2015-01-24 16:33 ` [PATCH 2/4] defconfigs: remove CONFIG_MTD_PARTITIONS Semen Protsenko
2015-01-24 16:33 ` [PATCH 3/4] defconfigs: remove CONFIG_MTD_CHAR Semen Protsenko
2015-01-24 16:33 ` [PATCH 4/4] defconfigs: remove CONFIG_MTD_DEBUG* Semen Protsenko
2015-01-24 16:49 ` [PATCH 0/4] defconfigs: cleanup obsolete MTD configs Paul Bolle
2015-01-24 20:54   ` Sam Protsenko
2015-01-28  1:04     ` Michael Ellerman [this message]
2015-01-26  8:38 ` Simon Horman

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=1422407074.32234.2.camel@ellerman.id.au \
    --to=mpe@ellerman.id.au \
    --cc=adi-buildroot-devel@lists.sourceforge.net \
    --cc=computersforpeace@gmail.com \
    --cc=dwmw2@infradead.org \
    --cc=egtvedt@samfundet.no \
    --cc=geert@linux-m68k.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=gxt@mprc.pku.edu.cn \
    --cc=hskinnemoen@gmail.com \
    --cc=linux-am33-list@redhat.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-m68k@lists.linux-m68k.org \
    --cc=linux-mips@linux-mips.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=linux-sh@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=pebolle@tiscali.nl \
    --cc=semen.protsenko@globallogic.com \
    --cc=yasutake.koichi@jp.panasonic.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