From: krzk@kernel.org (Krzysztof Kozlowski)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: samsung: Save defconfig for Exynos, S3C and S5P configs
Date: Thu, 8 Jun 2017 08:45:20 +0200 [thread overview]
Message-ID: <20170608064520.GA2770@kozik-book> (raw)
In-Reply-To: <CAK8P3a2_rLigHqnOkHPM+x2GDrwdGnwJOqEbY7YTsQRUXT_eJg@mail.gmail.com>
On Wed, Jun 07, 2017 at 09:49:58PM +0200, Arnd Bergmann wrote:
> On Wed, Jun 7, 2017 at 8:18 PM, Krzysztof Kozlowski <krzk@kernel.org> wrote:
> > Some configs for Samsung ARM SoCs were not updated for some time and
> > they still contain obsolete Kconfig entries. Generate new defconfig for
> > all Samsung ARM architectures (Exynos, S3C24xx, S3C64xx, S5Pv210).
> >
> > Signed-off-by: Krzysztof Kozlowski <krzk@kernel.org>
>
> Hi Krzysztof,
>
> Updating the defconfig files is good, but I'm always a little unsure
> about loss of
> information when we do that. Would it be possible for you to split this patch
> into two halves, with one of them just reordering the entries that moved,
> and the second one removing the entries that have disappeared, with an
> explanation for why they are no longer there? That would let us see whether
> the change was intentional and avoid problems from renamed Kconfig
> symbols that are no longer enabled afterwards.
Splitting the change into two commits (reorder and removal) makes sense.
However getting the information why some things were removed, will
require more effort. I'll see what I can do.
Best regards,
Krzysztof
next prev parent reply other threads:[~2017-06-08 6:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-07 18:18 [PATCH] ARM: samsung: Save defconfig for Exynos, S3C and S5P configs Krzysztof Kozlowski
2017-06-07 19:49 ` Arnd Bergmann
2017-06-08 6:45 ` Krzysztof Kozlowski [this message]
2017-06-08 7:25 ` Arnd Bergmann
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=20170608064520.GA2770@kozik-book \
--to=krzk@kernel.org \
--cc=linux-arm-kernel@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).