From: Brian Norris <computersforpeace@gmail.com>
To: "Rafał Miłecki" <zajec5@gmail.com>
Cc: "David Woodhouse" <dwmw2@infradead.org>,
"Boris Brezillon" <boris.brezillon@free-electrons.com>,
"Marek Vasut" <marek.vasut@gmail.com>,
"Richard Weinberger" <richard@nod.at>,
"Cyrille Pitchen" <cyrille.pitchen@atmel.com>,
linux-mtd@lists.infradead.org,
"Hauke Mehrtens" <hauke@hauke-m.de>,
"Rafał Miłecki" <rafal@milecki.pl>
Subject: Re: [PATCH V2 1/2] mtd: bcm47xxpart: move TRX parsing code to separated function
Date: Thu, 9 Feb 2017 19:00:22 -0800 [thread overview]
Message-ID: <20170210030022.GA65051@google.com> (raw)
In-Reply-To: <20170110221525.9216-1-zajec5@gmail.com>
On Tue, Jan 10, 2017 at 11:15:24PM +0100, Rafał Miłecki wrote:
> From: Rafał Miłecki <rafal@milecki.pl>
>
> This change simplifies main parsing loop logic a bit. In future it may
> be useful for moving TRX support to separated module / parser (if we
> implement support for them at some point).
> Finally parsing TRX at the end puts us in a better position as we have
> better flash layout knowledge. It may be useful e.g. if it appears there
> is more than 1 TRX partition.
>
> Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
> ---
> V2: Keep using bcm47xxpart_add_part in new parsing function
Applied both to l2-mtd.git
prev parent reply other threads:[~2017-02-10 3:00 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-10 11:50 [PATCH 1/2] mtd: bcm47xxpart: move TRX parsing code to separated function Rafał Miłecki
2017-01-10 11:50 ` [PATCH 2/2] mtd: bcm47xxpart: support layouts with multiple TRX partitions Rafał Miłecki
2017-01-10 16:19 ` [PATCH 1/2] mtd: bcm47xxpart: move TRX parsing code to separated function Marek Vasut
2017-01-10 16:27 ` Rafał Miłecki
2017-01-10 17:42 ` Marek Vasut
2017-01-10 22:15 ` [PATCH V2 " Rafał Miłecki
2017-01-10 22:15 ` [PATCH V2 2/2] mtd: bcm47xxpart: support layouts with multiple TRX partitions Rafał Miłecki
2017-02-09 16:54 ` [PATCH V2 1/2] mtd: bcm47xxpart: move TRX parsing code to separated function Rafał Miłecki
2017-02-09 17:29 ` Marek Vasut
2017-02-09 17:28 ` Marek Vasut
2017-02-09 18:05 ` Rafał Miłecki
2017-02-09 18:21 ` Marek Vasut
2017-02-09 19:11 ` Boris Brezillon
2017-02-09 19:33 ` Marek Vasut
2017-02-10 3:00 ` 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=20170210030022.GA65051@google.com \
--to=computersforpeace@gmail.com \
--cc=boris.brezillon@free-electrons.com \
--cc=cyrille.pitchen@atmel.com \
--cc=dwmw2@infradead.org \
--cc=hauke@hauke-m.de \
--cc=linux-mtd@lists.infradead.org \
--cc=marek.vasut@gmail.com \
--cc=rafal@milecki.pl \
--cc=richard@nod.at \
--cc=zajec5@gmail.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 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.