From: robert.jarzmik@free.fr (Robert Jarzmik)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v5 0/9] mtd: sharpslpart partition parser
Date: Sun, 08 Oct 2017 11:53:11 +0200 [thread overview]
Message-ID: <87376uezjs.fsf@belgarion.home> (raw)
In-Reply-To: <87inh6pw9e.fsf@belgarion.home> (Robert Jarzmik's message of "Tue, 29 Aug 2017 11:18:37 +0200")
Robert Jarzmik <robert.jarzmik@free.fr> writes:
> Boris Brezillon <boris.brezillon@free-electrons.com> writes:
>
>> Hi Robert,
>> Wait a bit before applying. I think patches 6 to 9 have a dependency on
>> patch 1 (it's not a build dependency, but NAND partitioning might be
>> wrong if you apply them), so we need to sync. What release is
>> pxa/for-next targeting? If it's 4.15 I can apply patch 1 just after
>> 4.14-rc1 is out and provide an immutable branch for you to pull in
>> pxa/for-next.
>
> Hi Boris,
>
> It's targeting 4.15 right now. And we can do as you like, either an immutable
> branch, or I wait to include these patches into my pxa/for-next until you give
> me your go, it's as you like.
Hi Boris,
So what's the status about the sync, should I pick the patches, and have the
others make it to your for-next branch ?
Cheers.
--
Robert
next prev parent reply other threads:[~2017-10-08 9:53 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-14 20:48 [PATCH v5 0/9] mtd: sharpslpart partition parser Andrea Adami
2017-08-14 20:48 ` [PATCH v5 1/9] mtd: sharpslpart: Add " Andrea Adami
2017-08-17 8:10 ` Boris Brezillon
2017-08-14 20:48 ` [PATCH v5 2/9] mtd: nand: sharpsl: Add partition parsers platform data Andrea Adami
2017-08-14 20:48 ` [PATCH v5 3/9] mfd: tmio: " Andrea Adami
2017-08-15 6:58 ` Lee Jones
2017-08-19 7:26 ` Boris Brezillon
2017-08-19 9:21 ` Boris Brezillon
2017-08-21 7:27 ` Lee Jones
2017-08-19 8:23 ` Wolfram Sang
2017-08-14 20:48 ` [PATCH v5 4/9] mtd: nand: sharpsl: Register partitions using the parsers Andrea Adami
2017-08-14 20:48 ` [PATCH v5 5/9] mtd: nand: tmio: " Andrea Adami
2017-08-19 8:22 ` Wolfram Sang
2017-08-14 20:48 ` [PATCH v5 6/9] ARM: pxa/corgi: Remove hardcoded partitioning, use sharpslpart parser Andrea Adami
2017-08-14 20:48 ` [PATCH v5 7/9] ARM: pxa/tosa: " Andrea Adami
2017-08-14 20:48 ` [PATCH v5 8/9] ARM: pxa/spitz: " Andrea Adami
2017-08-14 20:48 ` [PATCH v5 9/9] ARM: pxa/poodle: " Andrea Adami
2017-08-21 20:13 ` [PATCH v5 0/9] mtd: sharpslpart partition parser Boris Brezillon
2017-08-23 19:33 ` Robert Jarzmik
2017-08-24 9:33 ` Andrea Adami
2017-08-24 9:46 ` Boris Brezillon
2017-08-29 9:18 ` Robert Jarzmik
2017-10-08 9:53 ` Robert Jarzmik [this message]
2017-10-08 10:09 ` Boris Brezillon
2017-10-08 10:34 ` Boris Brezillon
2017-11-08 7:54 ` Boris Brezillon
2017-11-09 7:27 ` Robert Jarzmik
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=87376uezjs.fsf@belgarion.home \
--to=robert.jarzmik@free.fr \
--cc=linux-arm-kernel@lists.infradead.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).