All of lore.kernel.org
 help / color / mirror / Atom feed
From: Simon Glass <sjg@chromium.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/4] tegra: Remove merge markers in some Kconfig files
Date: Fri, 4 Dec 2015 10:25:28 -0700	[thread overview]
Message-ID: <CAPnjgZ04eqzzy+-tZRxqq_TEVysRneb3XJd_Rd=sLZPtTeOmoQ@mail.gmail.com> (raw)
In-Reply-To: <5661CA72.20307@wwwdotorg.org>

Hi Stephen,

On 4 December 2015 at 10:16, Stephen Warren <swarren@wwwdotorg.org> wrote:
> On 12/04/2015 08:58 AM, Simon Glass wrote:
>>
>> These were added by mistake in commit fde7e189. They cause a warning when
>> configuring the boards. Remove them.
>
>
> Patches 1-3,
> Tested-by: Stephen Warren <swarren@nvidia.com>
>
> It would be useful to include the appropriate Fixes: tags in the commit
> message, and this issue was originally:
>
> Reported-by: Kevin Hilman <khilman@linaro.org>

Thanks - what Fixes tags?

Regards,
Simon

  reply	other threads:[~2015-12-04 17:25 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-04 15:58 [U-Boot] [PATCH 1/4] tegra: Remove merge markers in some Kconfig files Simon Glass
2015-12-04 15:58 ` [U-Boot] [PATCH 2/4] dm: serial: ns16550: Add pre-reloc flag to the driver Simon Glass
2015-12-05  5:53   ` Thomas Chou
2015-12-06 22:08   ` [U-Boot] [U-Boot, " Tom Rini
2015-12-04 15:58 ` [U-Boot] [PATCH 3/4] dm: tegra: Provide serial platform data for SPL Simon Glass
2015-12-05  5:53   ` Thomas Chou
2015-12-06 22:08   ` [U-Boot] [U-Boot, " Tom Rini
2015-12-04 15:58 ` [U-Boot] [PATCH 4/4] dm: omap: Fix serial UART on beaglebone black Simon Glass
2015-12-05  5:54   ` Thomas Chou
2015-12-06 14:17   ` Tom Rini
2015-12-06 16:41     ` Simon Glass
2015-12-04 17:16 ` [U-Boot] [PATCH 1/4] tegra: Remove merge markers in some Kconfig files Stephen Warren
2015-12-04 17:25   ` Simon Glass [this message]
2015-12-04 20:08     ` Stephen Warren
2015-12-05  5:52 ` Thomas Chou
2015-12-06 22:08 ` [U-Boot] [U-Boot, " Tom Rini

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='CAPnjgZ04eqzzy+-tZRxqq_TEVysRneb3XJd_Rd=sLZPtTeOmoQ@mail.gmail.com' \
    --to=sjg@chromium.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.