From: Brian Norris <computersforpeace@gmail.com>
To: Clay McClure <clay@daemons.net>
Cc: Ray Jui <rjui@broadcom.com>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
Florian Fainelli <f.fainelli@gmail.com>,
Scott Branden <sbranden@broadcom.com>,
"bcm-kernel-feedback-list@broadcom.com"
<bcm-kernel-feedback-list@broadcom.com>
Subject: Re: [PATCH] mtd: brcmnand: Fix NAND_CMD_PARAM byte order
Date: Mon, 2 Nov 2015 15:30:54 -0800 [thread overview]
Message-ID: <20151102233054.GH7274@google.com> (raw)
In-Reply-To: <CAOVqfW_HXf9E4JNBHOCgAk7rpGexhpKHyfrQvSR7e3poiSHi2A@mail.gmail.com>
On Mon, Nov 02, 2015 at 03:10:05PM -0800, Clay McClure wrote:
> On Tue, Oct 27, 2015 at 1:40 PM, Brian Norris
> <computersforpeace@gmail.com> wrote:
> >
> > OK, getting testing feedback from an iProc-based system using ONFI would
> > be somewhat illuminating.
>
> I've tested your refactoring patch [1] on Helix4 (an iProc-based
> switch chip); seems to work fine.
You mean, you tested with a combo of my [1] and either [2] or [3]? Can I
get a 'Tested-by' line to add to them?
e.g.: 'Tested-by: Your Name <your@email>'
Regards,
Brian
>
> [1] http://patchwork.ozlabs.org/patch/536148/
[2] http://patchwork.ozlabs.org/patch/539145/ (except your patch is
whitespace damaged and patchwork didn't like it)
[3] http://patchwork.ozlabs.org/patch/535330/
prev parent reply other threads:[~2015-11-02 23:31 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-23 19:47 [PATCH] mtd: brcmnand: Fix NAND_CMD_PARAM byte order Clay McClure
2015-10-23 23:27 ` Brian Norris
2015-10-24 0:48 ` Ray Jui
2015-10-24 1:12 ` Brian Norris
2015-10-24 1:15 ` Brian Norris
[not found] ` <CAOVqfW-1YurDwJbKDgUJdQZVxJ_rWDg-x+28++SZtg-vPO4kYg@mail.gmail.com>
2015-10-26 18:14 ` Brian Norris
2015-10-26 18:52 ` Ray Jui
2015-10-26 20:08 ` Clay McClure
2015-10-27 20:40 ` Brian Norris
2015-10-27 20:55 ` Ray Jui
2015-11-02 23:05 ` Clay McClure
2015-11-04 2:04 ` Brian Norris
2015-11-05 0:37 ` Ray Jui
2015-11-02 23:10 ` Clay McClure
2015-11-02 23:30 ` Brian Norris [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=20151102233054.GH7274@google.com \
--to=computersforpeace@gmail.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=clay@daemons.net \
--cc=f.fainelli@gmail.com \
--cc=linux-mtd@lists.infradead.org \
--cc=rjui@broadcom.com \
--cc=sbranden@broadcom.com \
/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;
as well as URLs for NNTP newsgroup(s).