public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Marek Vasut <marex@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/6] arm: socfpga: scan: Clean up scan_chain_engine_is_idle()
Date: Wed, 5 Aug 2015 21:57:40 +0200	[thread overview]
Message-ID: <201508052157.40906.marex@denx.de> (raw)
In-Reply-To: <1438611733-7373-1-git-send-email-marex@denx.de>

On Monday, August 03, 2015 at 04:22:08 PM, Marek Vasut wrote:
> Rework this function so it's clear that it is only polling for certain
> bits to be cleared. Add kerneldoc. Fix it's return value to be either
> 0 on success and -ETIMEDOUT on error and propagate this through the
> scan manager code.
> 
> Signed-off-by: Marek Vasut <marex@denx.de>

Hi Dinh,

in case you missed this small patchset :-)

Best regards,
Marek Vasut

  parent reply	other threads:[~2015-08-05 19:57 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-03 14:22 [U-Boot] [PATCH 1/6] arm: socfpga: scan: Clean up scan_chain_engine_is_idle() Marek Vasut
2015-08-03 14:22 ` [U-Boot] [PATCH 2/6] arm: socfpga: scan: Introduce generic JTAG accessor Marek Vasut
2015-08-07 20:27   ` Dinh Nguyen
2015-08-03 14:22 ` [U-Boot] [PATCH 3/6] arm: socfpga: scan: Clean up horrible macros Marek Vasut
2015-08-07 20:40   ` Dinh Nguyen
2015-08-03 14:22 ` [U-Boot] [PATCH 4/6] arm: socfpga: scan: Factor out IO chain programming Marek Vasut
2015-08-07 20:52   ` Dinh Nguyen
2015-08-03 14:22 ` [U-Boot] [PATCH 5/6] arm: socfpga: scan: Add code to get FPGA ID Marek Vasut
2015-08-03 14:22 ` [U-Boot] [PATCH 6/6] arm: socfpga: misc: Add support for printing FPGA type Marek Vasut
2015-08-05 19:57 ` Marek Vasut [this message]
2015-08-07 20:26 ` [U-Boot] [PATCH 1/6] arm: socfpga: scan: Clean up scan_chain_engine_is_idle() Dinh Nguyen
2015-08-08 12:14   ` Marek Vasut
2015-08-08 12:15 ` Marek Vasut

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=201508052157.40906.marex@denx.de \
    --to=marex@denx.de \
    --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