From: Simon Glass <sjg@chromium.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/4 v2] common/console.c: Drop sandbox special-case console code
Date: Mon, 16 Nov 2015 14:08:09 -0700 [thread overview]
Message-ID: <CAPnjgZ3ySp3OC+wLbcjEVM_oSryG6VG6QMOdvg7jPP1V=HhxNQ@mail.gmail.com> (raw)
In-Reply-To: <1447683994-25930-1-git-send-email-sr@denx.de>
On 16 November 2015 at 07:26, Stefan Roese <sr@denx.de> wrote:
> As done in commit da229e4e [sandbox: Drop special-case sandbox console code],
> this patch drops the sandbox special-case code in vprintf() that was
> missed by Simon at that time.
>
> Signed-off-by: Stefan Roese <sr@denx.de>
> Cc: Simon Glass <sjg@chromium.org>
> ---
> v2:
> - new patch
>
> common/console.c | 5 -----
> 1 file changed, 5 deletions(-)
Acked-by: Simon Glass <sjg@chromium.org>
next prev parent reply other threads:[~2015-11-16 21:08 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-16 14:26 [U-Boot] [PATCH 1/4 v2] common/console.c: Drop sandbox special-case console code Stefan Roese
2015-11-16 14:26 ` [U-Boot] [PATCH 2/4 v2] common/console.c: Small coding style cleanup Stefan Roese
2015-11-16 21:08 ` Simon Glass
2015-11-23 22:44 ` [U-Boot] [U-Boot, 2/4, " Tom Rini
2015-11-16 14:26 ` [U-Boot] [PATCH 3/4 v2] lib/tiny-printf.c: Add tiny printf function for space limited environments Stefan Roese
2015-11-21 3:27 ` Tom Rini
2015-11-23 5:50 ` Stefan Roese
2015-11-16 14:26 ` [U-Boot] [PATCH 4/4 v2] lib/tiny-printf.c: Support numbers bigger than 0xffff and misc updates Stefan Roese
2015-11-23 22:44 ` [U-Boot] [U-Boot, 4/4, " Tom Rini
2015-11-16 21:08 ` Simon Glass [this message]
2015-11-23 6:00 ` [U-Boot] [PATCH 3/4 v3] lib/tiny-printf.c: Add tiny printf function for space limited environments Stefan Roese
2015-11-23 22:44 ` [U-Boot] [U-Boot, 3/4, " Tom Rini
2015-11-23 22:44 ` [U-Boot] [U-Boot, 1/4, v2] common/console.c: Drop sandbox special-case console code 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='CAPnjgZ3ySp3OC+wLbcjEVM_oSryG6VG6QMOdvg7jPP1V=HhxNQ@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.