All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stewart Smith <stewart@linux.vnet.ibm.com>
To: Michael Tritz <mtritz@us.ibm.com>,
	skiboot@lists.ozlabs.org, openbmc@lists.ozlabs.org
Cc: Michael Tritz <mtritz@us.ibm.com>, cyrilbur@gmail.com
Subject: Re: [PATCH v8] pflash option to retrieve PNOR partition flags
Date: Tue, 18 Jul 2017 18:19:13 +1000	[thread overview]
Message-ID: <874luacg3i.fsf@linux.vnet.ibm.com> (raw)
In-Reply-To: <20170712203149.12123-1-mtritz@us.ibm.com>

Michael Tritz <mtritz@us.ibm.com> writes:
> This commit extends pflash with an option to retrieve and print
> information for a particular partition, including the content from
> "pflash -i" and a verbose list of set miscellaneous flags. -i option
> is also updated to print a short list of flags in addition to the
> ECC flag, with one character per flag. A test of the new option is
> included in libflash/test.
>
> V8: Make check target now depends on having built pflash. Updated 
>     the path to pflash in the test script. Test script runs now.
> V7: Fixed whitespace error and changed permissions on test script
> V6: Reverted change to has_ecc() to avoid breaking libffs
>
> Change-Id: Iebb8a6d34c537cecd2eb44ddf41271c8fbe25258
> Signed-off-by: Michael Tritz <mtritz@us.ibm.com>

Thanks! I made a few minor changes to how the test was run (including
going and fixing up some of our code coverage infrasturcture) and merged
to master as of 360d0a394d8ce8f2f4cd0573cd51c56784f6faa4.

-- 
Stewart Smith
OPAL Architect, IBM.

      parent reply	other threads:[~2017-07-18  8:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-12 20:31 [PATCH v8] pflash option to retrieve PNOR partition flags Michael Tritz
2017-07-13  1:38 ` Cyril Bur
2017-07-18  8:19 ` Stewart Smith [this message]

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=874luacg3i.fsf@linux.vnet.ibm.com \
    --to=stewart@linux.vnet.ibm.com \
    --cc=cyrilbur@gmail.com \
    --cc=mtritz@us.ibm.com \
    --cc=openbmc@lists.ozlabs.org \
    --cc=skiboot@lists.ozlabs.org \
    /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.