From: Hauke Mehrtens <hauke@hauke-m.de>
To: Miquel Raynal <miquel.raynal@bootlin.com>
Cc: richard@nod.at, vigneshr@ti.com, robh+dt@kernel.org,
linux-mtd@lists.infradead.org, devicetree@vger.kernel.org,
rafal@milecki.pl, musashino.open@gmail.com
Subject: Re: [PATCH 1/2] mtd: parsers: trx: Allow to specify trx-magic in DT
Date: Sun, 18 Apr 2021 18:53:25 +0200 [thread overview]
Message-ID: <0934457e-5f8e-dd9b-bd14-de93c5eb06ec@hauke-m.de> (raw)
In-Reply-To: <20210317102556.68b76e96@xps13>
On 3/17/21 10:25 AM, Miquel Raynal wrote:
> Hi Hauke,
>
> Hauke Mehrtens <hauke@hauke-m.de> wrote on Mon, 15 Mar 2021 18:07:10
> +0100:
>
>> Buffalo uses a different TRX magic for every device, to be able to use
>> this trx parser, make it possible to specify the TRX magic in device
>> tree. If no TRX magic is specified in device tree, the standard value
>> will be used. This value should only be specified if a vendor chooses to
>> use a non standard TRX magic.
>>
>> Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
>> ---
>> .../bindings/mtd/partitions/brcm,trx.txt | 5 +++++
>> drivers/mtd/parsers/parser_trx.c | 21 ++++++++++++++++++-
>
> Can you please split this patch:
> 1- dt-binding update
> 2- driver update
>
> This way we can collect Rob's ack for the binding patch.
>
Hi,
Sorry for answering so late.
I will split this into two patches.
Hauke
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
next prev parent reply other threads:[~2021-04-18 16:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-15 17:07 [PATCH 0/2] mtd: parsers: trx: Add support for Buffalo WSR-2533DHP2 Hauke Mehrtens
2021-03-15 17:07 ` [PATCH 1/2] mtd: parsers: trx: Allow to specify trx-magic in DT Hauke Mehrtens
2021-03-17 9:25 ` Miquel Raynal
2021-04-18 16:53 ` Hauke Mehrtens [this message]
2021-03-18 6:43 ` Rafał Miłecki
2021-04-18 16:59 ` Hauke Mehrtens
2021-03-15 17:07 ` [PATCH 2/2] mtd: parsers: trx: Remove dependency to BRCM architectures Hauke Mehrtens
2021-03-18 6:45 ` Rafał Miłecki
2021-04-18 17:03 ` Hauke Mehrtens
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=0934457e-5f8e-dd9b-bd14-de93c5eb06ec@hauke-m.de \
--to=hauke@hauke-m.de \
--cc=devicetree@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=miquel.raynal@bootlin.com \
--cc=musashino.open@gmail.com \
--cc=rafal@milecki.pl \
--cc=richard@nod.at \
--cc=robh+dt@kernel.org \
--cc=vigneshr@ti.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).