From: Lee Jones <lee@kernel.org>
To: Pinkesh Vaghela <pinkesh.vaghela@einfochips.com>
Cc: Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Paul Walmsley <pjw@kernel.org>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>,
Alexandre Ghiti <alex@ghiti.fr>,
Andi Shyti <andi.shyti@kernel.org>,
Mika Westerberg <mika.westerberg@linux.intel.com>,
"linux-i2c@vger.kernel.org" <linux-i2c@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-riscv@lists.infradead.org"
<linux-riscv@lists.infradead.org>,
Min Lin <linmin@eswincomputing.com>,
Yulin Lu <luyulin@eswincomputing.com>,
Samuel Holland <samuel.holland@sifive.com>,
Darshan Prajapati <darshan.prajapati@einfochips.com>,
Pritesh Patel <pritesh.patel@einfochips.com>
Subject: Re: [PATCH v2 4/8] dt-bindings: mfd: syscon: add ESWIN EIC7700 compatible
Date: Wed, 22 Jul 2026 13:55:07 +0100 [thread overview]
Message-ID: <20260722125507.GD11805@google.com> (raw)
In-Reply-To: <SJ2PR04MB88965A802336D3FB947B736083C32@SJ2PR04MB8896.namprd04.prod.outlook.com>
On Mon, 20 Jul 2026, Pinkesh Vaghela wrote:
> Hi Lee,
>
> On Thursday, July 16, 2026 5:59 PM, Lee Jones wrote:
> > On Mon, 06 Jul 2026, Pinkesh Vaghela wrote:
> >
> > > Document ESWIN EIC7700 SoC compatible for syscon registers.
> > >
> > > Acked-by: Conor Dooley <conor.dooley@microchip.com>
> > > Signed-off-by: Pinkesh Vaghela <pinkesh.vaghela@einfochips.com>
> > > ---
> > > Documentation/devicetree/bindings/mfd/syscon.yaml | 2 ++
> > > 1 file changed, 2 insertions(+)
> >
> > Still doesn't apply. What tree did you rebase on?
> >
> > Whatever you rebase on needs to have the following commit:
> >
> > 1d02f2a79ebe ("dt-bindings: mfd: syscon: Drop custom select for older
> > dtschema")
>
> We rebased the patches to v7.2-rc2 on master branch of mainline tree
> before sending v2.
> We see that the patch series you are referring to is not present in
> v7.2-rc4 as well. However, they are present in linux-next.
>
> Could you please suggest on which tree should I rebase and send this patch?
Mainline lags Next by quite a few commits.
You should generally use Next or the Subsystem tree you are working on.
95 times out of 100 Next is fine.
--
Lee Jones
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2026-07-22 12:55 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-06 8:10 [PATCH v2 0/8] riscv: eswin: eic7700: Add support for clocks, resets, pinctrl, HSP bus, I2C and watchdog Pinkesh Vaghela
2026-07-06 8:10 ` [PATCH v2 1/8] riscv: dts: eswin: add reset generator for EIC7700 SoC Pinkesh Vaghela
2026-07-06 8:10 ` [PATCH v2 2/8] riscv: dts: eswin: add clock " Pinkesh Vaghela
2026-07-06 8:10 ` [PATCH v2 3/8] riscv: dts: eswin: eic7700: add pinctrl support Pinkesh Vaghela
2026-07-06 8:10 ` [PATCH v2 4/8] dt-bindings: mfd: syscon: add ESWIN EIC7700 compatible Pinkesh Vaghela
2026-07-16 12:28 ` Lee Jones
2026-07-20 13:28 ` Pinkesh Vaghela
2026-07-22 12:55 ` Lee Jones [this message]
2026-07-06 8:10 ` [PATCH v2 5/8] riscv: dts: eswin: add hsp bus node Pinkesh Vaghela
2026-07-06 8:10 ` [PATCH v2 6/8] dt-bindings: i2c: dw: add ESWIN EIC7700 SoC I2C controller Pinkesh Vaghela
2026-07-06 16:59 ` Conor Dooley
2026-07-06 8:10 ` [PATCH v2 7/8] riscv: dts: eswin: add I2C controller support Pinkesh Vaghela
2026-07-06 8:10 ` [PATCH v2 8/8] riscv: dts: eswin: add watchdog support Pinkesh Vaghela
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=20260722125507.GD11805@google.com \
--to=lee@kernel.org \
--cc=alex@ghiti.fr \
--cc=andi.shyti@kernel.org \
--cc=aou@eecs.berkeley.edu \
--cc=conor+dt@kernel.org \
--cc=darshan.prajapati@einfochips.com \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linmin@eswincomputing.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=luyulin@eswincomputing.com \
--cc=mika.westerberg@linux.intel.com \
--cc=palmer@dabbelt.com \
--cc=pinkesh.vaghela@einfochips.com \
--cc=pjw@kernel.org \
--cc=pritesh.patel@einfochips.com \
--cc=robh@kernel.org \
--cc=samuel.holland@sifive.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