From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/5] ARM: config: Regenerate multi_v5_defconfig
Date: Wed, 02 Dec 2015 16:10:58 +0100 [thread overview]
Message-ID: <1799595.aerWlahiX8@wuerfel> (raw)
In-Reply-To: <20151202150801.GL29814@lunn.ch>
On Wednesday 02 December 2015 16:08:01 Andrew Lunn wrote:
>
> Humm, i wounder if 0-day could be of use here. How about at the end of
> each patch series, it regenerates the _defconfig files. If there are
> any changes, issue a warning. That will help keep them in sync with
> reality.
Sounds like a good idea, but it will have to regenerate the defconfig files
before and after and see if there are additional changes.
Arnd
next prev parent reply other threads:[~2015-12-02 15:10 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-01 23:33 [PATCH 0/5] multi and mvebu v5 defconfig updates Andrew Lunn
2015-12-01 23:33 ` [PATCH 1/5] ARM: config: Regenerate multi_v5_defconfig Andrew Lunn
2015-12-02 13:44 ` Arnd Bergmann
2015-12-02 14:17 ` Andrew Lunn
2015-12-02 14:57 ` Arnd Bergmann
2015-12-02 15:08 ` Andrew Lunn
2015-12-02 15:10 ` Arnd Bergmann [this message]
2015-12-01 23:33 ` [PATCH 2/5] ARM: config: Reenable DSA in multi_v5_defconfig Andrew Lunn
2015-12-02 13:44 ` Arnd Bergmann
2015-12-01 23:33 ` [PATCH 3/5] ARM: config: Add orion5x to multi_v5_defconfig Andrew Lunn
2015-12-01 23:33 ` [PATCH 4/5] ARM: mvebu: Reenable DSA in mvebu_v5_defconfig Andrew Lunn
2015-12-07 17:02 ` Gregory CLEMENT
2015-12-01 23:33 ` [PATCH 5/5] ARM: mvebu: update v5 defconfig for Orion5x machines Andrew Lunn
2015-12-07 17:03 ` Gregory CLEMENT
2015-12-07 17:06 ` [PATCH 0/5] multi and mvebu v5 defconfig updates Gregory CLEMENT
2015-12-07 22:57 ` Arnd Bergmann
2015-12-08 9:55 ` Gregory CLEMENT
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=1799595.aerWlahiX8@wuerfel \
--to=arnd@arndb.de \
--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