From: Boris Brezillon <boris.brezillon@free-electrons.com>
To: Robert Jarzmik <robert.jarzmik@free.fr>
Cc: Andrea Adami <andrea.adami@gmail.com>,
linux-mtd@lists.infradead.org,
Wolfram Sang <wsa+renesas@sang-engineering.com>,
Dmitry Eremin-Solenikov <dbaryshkov@gmail.com>,
Richard Weinberger <richard@nod.at>,
linux-mmc@vger.kernel.org, Russell King <linux@armlinux.org.uk>,
Haojian Zhuang <haojian.zhuang@gmail.com>,
linux-kernel@vger.kernel.org, Marek Vasut <marek.vasut@gmail.com>,
linux-arm-kernel@lists.infradead.org,
Cyrille Pitchen <cyrille.pitchen@wedev4u.fr>,
Lee Jones <lee.jones@linaro.org>,
Brian Norris <computersforpeace@gmail.com>,
David Woodhouse <dwmw2@infradead.org>,
Linus Walleij <linus.walleij@linaro.org>,
Daniel Mack <daniel@zonque.org>
Subject: Re: [PATCH v5 0/9] mtd: sharpslpart partition parser
Date: Wed, 8 Nov 2017 08:54:46 +0100 [thread overview]
Message-ID: <20171108085446.718a2ff5@bbrezillon> (raw)
In-Reply-To: <87376uezjs.fsf@belgarion.home>
On Sun, 08 Oct 2017 11:53:11 +0200
Robert Jarzmik <robert.jarzmik@free.fr> wrote:
> 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 ?
It's been merged in l2-mtd/master (our -next branch) which is
targeting 4.15. Unfortunately we didn't create a topic branch, which
means you'll have to wait 4.15-rc1 before pushing patches 6 to 9 if you
want avoid regressions. Anyway, I guess it's already too late to send
PRs to arm-soc for 4.15.
WARNING: multiple messages have this Message-ID (diff)
From: boris.brezillon@free-electrons.com (Boris Brezillon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v5 0/9] mtd: sharpslpart partition parser
Date: Wed, 8 Nov 2017 08:54:46 +0100 [thread overview]
Message-ID: <20171108085446.718a2ff5@bbrezillon> (raw)
In-Reply-To: <87376uezjs.fsf@belgarion.home>
On Sun, 08 Oct 2017 11:53:11 +0200
Robert Jarzmik <robert.jarzmik@free.fr> wrote:
> 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 ?
It's been merged in l2-mtd/master (our -next branch) which is
targeting 4.15. Unfortunately we didn't create a topic branch, which
means you'll have to wait 4.15-rc1 before pushing patches 6 to 9 if you
want avoid regressions. Anyway, I guess it's already too late to send
PRs to arm-soc for 4.15.
next prev parent reply other threads:[~2017-11-08 7:54 UTC|newest]
Thread overview: 57+ 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 ` Andrea Adami
2017-08-14 20:48 ` [PATCH v5 1/9] mtd: sharpslpart: Add " Andrea Adami
2017-08-14 20:48 ` Andrea Adami
2017-08-14 20:48 ` Andrea Adami
2017-08-17 8:10 ` Boris Brezillon
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 ` Andrea Adami
2017-08-14 20:48 ` [PATCH v5 3/9] mfd: tmio: " Andrea Adami
2017-08-14 20:48 ` Andrea Adami
2017-08-15 6:58 ` Lee Jones
2017-08-15 6:58 ` Lee Jones
2017-08-19 7:26 ` Boris Brezillon
2017-08-19 7:26 ` Boris Brezillon
2017-08-19 9:21 ` Boris Brezillon
2017-08-19 9:21 ` Boris Brezillon
2017-08-21 7:27 ` Lee Jones
2017-08-21 7:27 ` Lee Jones
2017-08-19 8:23 ` Wolfram Sang
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 ` Andrea Adami
2017-08-14 20:48 ` Andrea Adami
2017-08-14 20:48 ` [PATCH v5 5/9] mtd: nand: tmio: " Andrea Adami
2017-08-14 20:48 ` Andrea Adami
2017-08-19 8:22 ` Wolfram Sang
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 ` Andrea Adami
2017-08-14 20:48 ` [PATCH v5 7/9] ARM: pxa/tosa: " Andrea Adami
2017-08-14 20:48 ` Andrea Adami
2017-08-14 20:48 ` [PATCH v5 8/9] ARM: pxa/spitz: " Andrea Adami
2017-08-14 20:48 ` Andrea Adami
2017-08-14 20:48 ` [PATCH v5 9/9] ARM: pxa/poodle: " Andrea Adami
2017-08-14 20:48 ` Andrea Adami
2017-08-21 20:13 ` [PATCH v5 0/9] mtd: sharpslpart partition parser Boris Brezillon
2017-08-21 20:13 ` Boris Brezillon
2017-08-23 19:33 ` Robert Jarzmik
2017-08-23 19:33 ` Robert Jarzmik
2017-08-24 9:33 ` Andrea Adami
2017-08-24 9:33 ` Andrea Adami
2017-08-24 9:46 ` Boris Brezillon
2017-08-24 9:46 ` Boris Brezillon
2017-08-29 9:18 ` Robert Jarzmik
2017-08-29 9:18 ` Robert Jarzmik
2017-10-08 9:53 ` Robert Jarzmik
2017-10-08 9:53 ` Robert Jarzmik
2017-10-08 10:09 ` Boris Brezillon
2017-10-08 10:09 ` Boris Brezillon
2017-10-08 10:34 ` Boris Brezillon
2017-10-08 10:34 ` Boris Brezillon
2017-11-08 7:54 ` Boris Brezillon [this message]
2017-11-08 7:54 ` Boris Brezillon
2017-11-09 7:27 ` Robert Jarzmik
2017-11-09 7:27 ` Robert Jarzmik
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=20171108085446.718a2ff5@bbrezillon \
--to=boris.brezillon@free-electrons.com \
--cc=andrea.adami@gmail.com \
--cc=computersforpeace@gmail.com \
--cc=cyrille.pitchen@wedev4u.fr \
--cc=daniel@zonque.org \
--cc=dbaryshkov@gmail.com \
--cc=dwmw2@infradead.org \
--cc=haojian.zhuang@gmail.com \
--cc=lee.jones@linaro.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=linux@armlinux.org.uk \
--cc=marek.vasut@gmail.com \
--cc=richard@nod.at \
--cc=robert.jarzmik@free.fr \
--cc=wsa+renesas@sang-engineering.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.