From: Timothy Pearson <tpearson@raptorengineering.com>
To: "Rafał Miłecki" <zajec5@gmail.com>
Cc: linux-mtd@lists.infradead.org,
Stewart Smith <stewart@linux.vnet.ibm.com>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>
Subject: Re: [PATCH] mtd/powernv_flash: Enable partition support
Date: Mon, 23 Jul 2018 13:19:53 -0500 [thread overview]
Message-ID: <5B561C49.6040208@raptorengineering.com> (raw)
In-Reply-To: <CACna6ryaT7Q=FSH_UBs5p6H3VdkpeKH_AYbQ=_WPB7N3xqoaOg@mail.gmail.com>
On 07/23/2018 05:14 AM, Rafał Miłecki wrote:
> On Mon, 23 Jul 2018 at 11:02, Timothy Pearson
> <tpearson@raptorengineering.com> wrote:
>> On certain systems, such as the Talos II, skiboot emits a partition
>> table for the main PNOR MTD device in the generated device tree.
>>
>> Allow this partition table to be parsed and the partitions to be
>> exposed via MTD device partition nodes.
>>
>> Signed-off-by: Timothy Pearson <tpearson@raptorengineering.com>
>
> This already has been handled in the:
> [PATCH] mtd: powernv_flash: set of_node in mtd's dev
> https://patchwork.ozlabs.org/patch/943327/
>
> I marked you as reporter, I Cc-ed you, Boris replied to it. I didn't
> expect you to miss that change.
Thank you for the information. I did miss the change, not sure how, so
my apologies.
--
Timothy Pearson
Raptor Engineering
+1 (415) 727-8645 (direct line)
+1 (512) 690-0200 (switchboard)
https://www.raptorengineering.com
next prev parent reply other threads:[~2018-07-23 18:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-23 9:02 [PATCH] mtd/powernv_flash: Enable partition support Timothy Pearson
2018-07-23 10:14 ` Rafał Miłecki
2018-07-23 18:19 ` Timothy Pearson [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-03-25 20:05 Timothy Pearson
2018-03-29 5:29 ` Rafał Miłecki
2018-03-29 21:43 ` Timothy Pearson
2018-03-29 22:11 ` Rafał Miłecki
2018-03-29 22:25 ` Timothy Pearson
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=5B561C49.6040208@raptorengineering.com \
--to=tpearson@raptorengineering.com \
--cc=benh@kernel.crashing.org \
--cc=linux-mtd@lists.infradead.org \
--cc=stewart@linux.vnet.ibm.com \
--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.