[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <ZFOXvQAjA5bri+Zb@yilunxu-OptiPlex-7050>
Date: Thu, 4 May 2023 19:32:13 +0800
From: Xu Yilun <yilun.xu@...el.com>
To: Ivan Bornyakov <i.bornyakov@...rotek.ru>
Cc: Rob Herring <robh@...nel.org>, linux-kernel@...r.kernel.org,
Moritz Fischer <mdf@...nel.org>, Wu Hao <hao.wu@...el.com>,
Tom Rix <trix@...hat.com>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
Conor Dooley <conor.dooley@...rochip.com>,
Vladimir Georgiev <v.georgiev@...rotek.ru>, system@...rotek.ru,
linux-fpga@...r.kernel.org, devicetree@...r.kernel.org
Subject: Re: [PATCH v2 2/2] dt-bindings: fpga: replace Ivan Bornyakov
maintainership
On 2023-04-29 at 11:29:19 +0300, Ivan Bornyakov wrote:
> On Fri, Apr 28, 2023 at 05:04:15PM -0500, Rob Herring wrote:
> > On Fri, Apr 28, 2023 at 05:01:50PM +0300, Ivan Bornyakov wrote:
> > > As I'm leaving Metrotek, hand over Lattice Slave SPI sysCONFIG FPGA
> > > manager and Microchip Polarfire FPGA manager maintainership duties to
> > > Vladimir.
> > >
> > > Signed-off-by: Ivan Bornyakov <i.bornyakov@...rotek.ru>
> > > Signed-off-by: Vladimir Georgiev <v.georgiev@...rotek.ru>
> >
> > The patch sender's Sob goes last. And only Vladimir should add his Sob
> > (when an author or sender).
> >
>
> For the moment, when I'm still sender, would it be alright if we replace
> Vladimir's "Signed-off-by" to "Acked-by"?
Yes. I actually need an "Acked-by" that sent from Vladimir.
>
> > > ---
> > > Documentation/devicetree/bindings/fpga/lattice,sysconfig.yaml | 2 +-
> > > .../devicetree/bindings/fpga/microchip,mpf-spi-fpga-mgr.yaml | 2 +-
> > > 2 files changed, 2 insertions(+), 2 deletions(-)
> > >
> > > diff --git a/Documentation/devicetree/bindings/fpga/lattice,sysconfig.yaml b/Documentation/devicetree/bindings/fpga/lattice,sysconfig.yaml
> > > index 4fb05eb84e2a..164331eb6275 100644
> > > --- a/Documentation/devicetree/bindings/fpga/lattice,sysconfig.yaml
> > > +++ b/Documentation/devicetree/bindings/fpga/lattice,sysconfig.yaml
> > > @@ -7,7 +7,7 @@ $schema: http://devicetree.org/meta-schemas/core.yaml#
> > > title: Lattice Slave SPI sysCONFIG FPGA manager
> > >
> > > maintainers:
> > > - - Ivan Bornyakov <i.bornyakov@...rotek.ru>
> > > + - Vladimir Georgiev <v.georgiev@...rotek.ru>
> > >
> > > description: |
> > > Lattice sysCONFIG port, which is used for FPGA configuration, among others,
> > > diff --git a/Documentation/devicetree/bindings/fpga/microchip,mpf-spi-fpga-mgr.yaml b/Documentation/devicetree/bindings/fpga/microchip,mpf-spi-fpga-mgr.yaml
> > > index 527532f039ce..a157eecfb5fc 100644
> > > --- a/Documentation/devicetree/bindings/fpga/microchip,mpf-spi-fpga-mgr.yaml
> > > +++ b/Documentation/devicetree/bindings/fpga/microchip,mpf-spi-fpga-mgr.yaml
> > > @@ -7,7 +7,7 @@ $schema: http://devicetree.org/meta-schemas/core.yaml#
> > > title: Microchip Polarfire FPGA manager.
> > >
> > > maintainers:
> > > - - Ivan Bornyakov <i.bornyakov@...rotek.ru>
> > > + - Vladimir Georgiev <v.georgiev@...rotek.ru>
> > >
> > > description:
> > > Device Tree Bindings for Microchip Polarfire FPGA Manager using slave SPI to
> > > --
> > > 2.40.0
> > >
> > >
>
Powered by blists - more mailing lists