public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Albert ARIBAUD <albert.u.boot@aribaud.net>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v5 1/3] Kconfig: Add EXPERT option
Date: Fri, 14 Nov 2014 09:55:41 +0100	[thread overview]
Message-ID: <20141114095541.0647d77c@lilith> (raw)
In-Reply-To: <1415954071-5934-2-git-send-email-hdegoede@redhat.com>

Hello Hans,

On Fri, 14 Nov 2014 09:34:29 +0100, Hans de Goede <hdegoede@redhat.com>
wrote:
> From: Tom Rini <trini@ti.com>
> 
> For similar reasons to why the Linux Kernel has an EXPERT option, we too
> want an option to allow for tweaking of some options that while normally
> should remain hidden, may need to be changed in some cases.
> 
> Signed-off-by: Tom Rini <trini@ti.com>
> Acked-by: Masahiro Yamada <yamada.m@jp.panasonic.com>
> Acked-by: Hans de Goede <hdegoede@redhat.com>
> Signed-off-by: Hans de Goede <hdegoede@redhat.com>
> ---

As you're just resending Tom's patch, should it have your own
Signed-off-by? No need to post v6 if you think this should be
corrected, I would do it when applying.

Amicalement,
-- 
Albert.

  reply	other threads:[~2014-11-14  8:55 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-14  8:34 [U-Boot] [PATCH v5 0/3] ARM: Add armv7/Kconfig and allow booting in secure mode on non-secure boot capable systems Hans de Goede
2014-11-14  8:34 ` [U-Boot] [PATCH v5 1/3] Kconfig: Add EXPERT option Hans de Goede
2014-11-14  8:55   ` Albert ARIBAUD [this message]
2014-11-14  8:58     ` Hans de Goede
2014-11-20 15:43       ` Tom Rini
2014-11-21  9:18         ` Albert ARIBAUD
2014-11-14  8:34 ` [U-Boot] [PATCH v5 2/3] ARM: Add arch/arm/cpu/armv7/Kconfig with non-secure and virt options Hans de Goede
2014-11-14  8:34 ` [U-Boot] [PATCH v5 3/3] ARM: bootm: Allow booting in secure mode on hyp capable systems Hans de Goede
2014-11-20 14:34 ` [U-Boot] [PATCH v5 0/3] ARM: Add armv7/Kconfig and allow booting in secure mode on non-secure boot " Hans de Goede

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=20141114095541.0647d77c@lilith \
    --to=albert.u.boot@aribaud.net \
    --cc=u-boot@lists.denx.de \
    /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