All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tim Chick <tim.chick@mediatek.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] debug_uart: Try not to use stack in printch
Date: Thu,  6 Apr 2017 16:32:41 +0100	[thread overview]
Message-ID: <1491492761-15722-1-git-send-email-tim.chick@mediatek.com> (raw)

Spam detection software, running on the system "lists.denx.de",
has identified this incoming email as possible spam.  The original
message has been attached to this so you can view it or label
similar future email.  If you have any questions, see
@@CONTACT_ADDRESS@@ for details.

Content preview:  Previous change to create _printch causes the stack to be
  used, breaking printch before stack is available. Inline _printch to prevent
   this happening. Signed-off-by: Tim Chick <tim.chick@mediatek.com> --- [...]
   

Content analysis details:   (6.3 points, 5.0 required)

 pts rule name              description
---- ---------------------- --------------------------------------------------
 0.7 RCVD_IN_XBL            RBL: Received via a relay in Spamhaus XBL
                            [188.29.165.105 listed in zen.spamhaus.org]
 3.6 RCVD_IN_PBL            RBL: Received via a relay in Spamhaus PBL
 1.6 RCVD_IN_BRBL_LASTEXT   RBL: No description available.
                            [188.29.165.105 listed in bb.barracudacentral.org]
 0.4 RDNS_DYNAMIC           Delivered to internal network by host with
                            dynamic-looking rDNS


-------------- next part --------------
An embedded message was scrubbed...
From: Tim Chick <tim.chick@mediatek.com>
Subject: [PATCH] debug_uart: Try not to use stack in printch
Date: Thu,  6 Apr 2017 16:32:41 +0100
Size: 1696
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20170406/c2ac6b54/attachment.mht>

             reply	other threads:[~2017-04-06 15:32 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-06 15:32 Tim Chick [this message]
2017-04-14 21:09 ` [U-Boot] debug_uart: Try not to use stack in printch 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=1491492761-15722-1-git-send-email-tim.chick@mediatek.com \
    --to=tim.chick@mediatek.com \
    --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.