From: Miquel Raynal <miquel.raynal@bootlin.com>
To: Mikhail Zhilkin <csharper2005@gmail.com>
Cc: Richard Weinberger <richard@nod.at>,
Vignesh Raghavendra <vigneshr@ti.com>,
Rob Herring <robh+dt@kernel.org>,
NOGUCHI Hiroshi <drvlabo@gmail.com>,
Hauke Mehrtens <hauke@hauke-m.de>, Karim <Karimdplay@gmail.com>,
M <x1@disroot.org>,
linux-mtd@lists.infradead.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org
Subject: Re: [PATCH] mtd: parsers: add support for Sercomm partitions
Date: Wed, 11 May 2022 09:16:43 +0200 [thread overview]
Message-ID: <20220511091643.064f9d13@xps13> (raw)
In-Reply-To: <ede9e050-3b60-ba0e-c626-044f7825adb7@gmail.com>
Hi Mikhail,
csharper2005@gmail.com wrote on Tue, 10 May 2022 23:07:23 +0300:
> Hi Miquel,
>
> On 3/30/2022 11:09 AM, Miquel Raynal wrote:
> > Hi Mikhail,
> >
> > csharper2005@gmail.com wrote on Tue, 29 Mar 2022 12:20:16 +0000:
> >
> >> This adds an MTD partition parser for the Sercomm partition table that
> >> is used in some Beeline, Netgear and Sercomm routers.
> >>
> >> The Sercomm partition map table contains real partition offsets, which
> >> may differ from device to device depending on the number and location of
> >> bad blocks on NAND.
> >>
> >> Device tree example:
> >> partitions {
> >> compatible = "sercomm,sc-partitions", "fixed-partitions";
> >> #address-cells = <1>;
> >> #size-cells = <1>;
> >>
> >> partition@0 {
> >> label = "u-boot";
> >> reg = <0x0 0x100000>;
> >> scpart-id = <0>;
> >> read-only;
> >> };
> >> };
> > You'll need a DT binding patch and Rob's ack!
>
> I hope that I near to finish with DT binding...
>
> Link:
> https://lore.kernel.org/all/20220510162314.20810-1-csharper2005@gmail.com/
>
> Link:
> https://lore.kernel.org/all/20220510162403.20861-1-csharper2005@gmail.com/
>
> >> This is essentially the same code as proposed by NOGUCHI Hiroshi
> >> <drvlabo@gmail.com> here:
> > I would credit Hiroshi with a Suggested-by at least
>
> I read submitting patches rules again and thought that Signed-off-by is
> suitable for this case. Is this ok?
Either you take his work almost like it is and he must be the author
*and* the first signed-off-by line, or you take the authorship if you
think you did enough modifications to the code and in this case you can
either credit him with a suggested-by before your signed-off, or you
can credit him with a co-developed-by + his signed-off and then yours.
>
> Link:
> https://lore.kernel.org/all/20220510162655.21011-1-csharper2005@gmail.com/
>
> >> https://github.com/openwrt/openwrt/pull/1318#issuecomment-420607394
> > And use a Link: tag for this.
> >
> Fixed, thanks!
>
> Link:
> https://lore.kernel.org/all/20220510162655.21011-1-csharper2005@gmail.com/
>
> > Thanks,
> > Miquèl
Thanks,
Miquèl
next prev parent reply other threads:[~2022-05-11 7:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-29 12:20 [PATCH] mtd: parsers: add support for Sercomm partitions Mikhail Zhilkin
2022-03-30 8:09 ` Miquel Raynal
2022-05-10 20:07 ` Mikhail Zhilkin
2022-05-11 7:16 ` Miquel Raynal [this message]
2022-05-11 20:36 ` Mikhail Zhilkin
2022-05-12 7:18 ` Miquel Raynal
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=20220511091643.064f9d13@xps13 \
--to=miquel.raynal@bootlin.com \
--cc=Karimdplay@gmail.com \
--cc=csharper2005@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=drvlabo@gmail.com \
--cc=hauke@hauke-m.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=richard@nod.at \
--cc=robh+dt@kernel.org \
--cc=vigneshr@ti.com \
--cc=x1@disroot.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 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).