Linux-FPGA Archive mirror
 help / color / mirror / Atom feed
From: Xu Yilun <yilun.xu@intel.com>
To: Ivan Bornyakov <i.bornyakov@metrotek.ru>
Cc: Rob Herring <robh@kernel.org>,
	linux-kernel@vger.kernel.org, Moritz Fischer <mdf@kernel.org>,
	Wu Hao <hao.wu@intel.com>, Tom Rix <trix@redhat.com>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	Conor Dooley <conor.dooley@microchip.com>,
	Vladimir Georgiev <v.georgiev@metrotek.ru>,
	system@metrotek.ru, linux-fpga@vger.kernel.org,
	devicetree@vger.kernel.org
Subject: Re: [PATCH v2 2/2] dt-bindings: fpga: replace Ivan Bornyakov maintainership
Date: Thu, 4 May 2023 19:32:13 +0800	[thread overview]
Message-ID: <ZFOXvQAjA5bri+Zb@yilunxu-OptiPlex-7050> (raw)
In-Reply-To: <20230429082919.i4pmerf4qeckl3w6@x260>

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@metrotek.ru>
> > > Signed-off-by: Vladimir Georgiev <v.georgiev@metrotek.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@metrotek.ru>
> > > +  - Vladimir Georgiev <v.georgiev@metrotek.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@metrotek.ru>
> > > +  - Vladimir Georgiev <v.georgiev@metrotek.ru>
> > >  
> > >  description:
> > >    Device Tree Bindings for Microchip Polarfire FPGA Manager using slave SPI to
> > > -- 
> > > 2.40.0
> > > 
> > > 
> 

  parent reply	other threads:[~2023-05-04  3:33 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-28 14:01 [PATCH v2 0/2] replace Ivan Bornyakov maintainership Ivan Bornyakov
2023-04-28 14:01 ` [PATCH v2 1/2] MAINTAINERS: update Microchip MPF FPGA reviewers Ivan Bornyakov
2023-04-28 14:01 ` [PATCH v2 2/2] dt-bindings: fpga: replace Ivan Bornyakov maintainership Ivan Bornyakov
2023-04-28 22:04   ` Rob Herring
2023-04-29  8:29     ` Ivan Bornyakov
2023-04-29 10:04       ` Conor Dooley
2023-05-04 11:32       ` Xu Yilun [this message]
2023-04-28 16:55 ` [PATCH v2 0/2] " Conor Dooley
2023-04-28 17:19   ` Ivan Bornyakov

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=ZFOXvQAjA5bri+Zb@yilunxu-OptiPlex-7050 \
    --to=yilun.xu@intel.com \
    --cc=conor.dooley@microchip.com \
    --cc=devicetree@vger.kernel.org \
    --cc=hao.wu@intel.com \
    --cc=i.bornyakov@metrotek.ru \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-fpga@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mdf@kernel.org \
    --cc=robh@kernel.org \
    --cc=system@metrotek.ru \
    --cc=trix@redhat.com \
    --cc=v.georgiev@metrotek.ru \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).