public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: olof@lixom.net (Olof Johansson)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] Renesas ARM Based SoC Defconfig Updates for v4.19
Date: Sat, 21 Jul 2018 15:03:43 -0700	[thread overview]
Message-ID: <20180721220343.yuwrfxz3fo25krzv@localhost> (raw)
In-Reply-To: <cover.1532086504.git.horms+renesas@verge.net.au>

On Fri, Jul 20, 2018 at 02:03:54PM +0200, Simon Horman wrote:
> Hi Olof, Hi Kevin, Hi Arnd,
> 
> Please consider these Renesas ARM based SoC defconfig updates for v4.19.
> 
> 
> The following changes since commit ce397d215ccd07b8ae3f71db689aedb85d56ab40:
> 
>   Linux 4.18-rc1 (2018-06-17 08:04:49 +0900)
> 
> are available in the git repository at:
> 
>   https://git.kernel.org/pub/scm/linux/kernel/git/horms/renesas.git tags/renesas-arm-defconfig-for-v4.19
> 
> for you to fetch changes up to e82c98d0448c60706a8024d460eadb9d7402dcba:
> 
>   ARM: multi_v7_defconfig: Enable support for RZN1D-DB (2018-07-13 10:15:20 +0200)
> 
> ----------------------------------------------------------------
> Renesas ARM Based SoC Defconfig Updates for v4.19
> 
> multi_v7_defconfig and shmobile_defconfig Enhancement:
> 
> * Enable support for recently upstreamed RZN1D-DB board
>   in multi_v7_defconfig and shmobile_defconfig. This is
>   to give better test coverage.
> 
> shmobile_defconfig Clean-Up:
> 
> * Drop NET_VENDOR_<FOO>=n
> 
>   This reduces the size of the defconfig without any change in the
>   resulting kernel config.
> 
> shmobile_defconfig Enhancements:
> 
> * Set CONFIG_LOCALVERSION to shmobile_defconfig
> 
>   This follows what appears to be common practice in defconfigs
>   and allows easier management of the kernel flavour at run-time.

I replied to the multi-versions of defconfig for this patch -- it's not a good
way to solve the problem of detecting config at runtime. Please drop this
patch. See:

https://lore.kernel.org/lkml/CAOesGMgkU6yBRpAsED2fPyuAo9Tc=YprndGdkmBVrc+0783VwQ at mail.gmail.com/


-Olof

  parent reply	other threads:[~2018-07-21 22:03 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-20 12:03 [GIT PULL] Renesas ARM Based SoC Defconfig Updates for v4.19 Simon Horman
2018-07-20 12:03 ` [PATCH 1/7] ARM: shmobile: defconfig: Enable MTD command line partition parsing Simon Horman
2018-07-20 12:03 ` [PATCH 2/7] ARM: shmobile: defconfig: Drop NET_VENDOR_<FOO>=n Simon Horman
2018-07-20 12:03 ` [PATCH 3/7] ARM: shmobile: defconfig: Enable reset controller support Simon Horman
2018-07-20 12:03 ` [PATCH 4/7] ARM: shmobile: defconfig: Enable support for RZN1D-DB Simon Horman
2018-07-20 12:03 ` [PATCH 5/7] ARM: shmobile: defconfig: Disable /sbin/hotplug fork-bomb Simon Horman
2018-07-20 12:03 ` [PATCH 6/7] ARM: shmobile: defconfig: Set CONFIG_LOCALVERSION Simon Horman
2018-07-20 12:03 ` [PATCH 7/7] ARM: multi_v7_defconfig: Enable support for RZN1D-DB Simon Horman
2018-07-21 22:03 ` Olof Johansson [this message]
2018-07-23  9:11   ` [GIT PULL] Renesas ARM Based SoC Defconfig Updates for v4.19 Geert Uytterhoeven
2018-07-23 16:22     ` Olof Johansson
2018-07-23 17:16       ` Geert Uytterhoeven
2018-07-23 11:17   ` 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=20180721220343.yuwrfxz3fo25krzv@localhost \
    --to=olof@lixom.net \
    --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