public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
To: Marc Zyngier <maz@kernel.org>
Cc: "Rob Herring" <robh+dt@kernel.org>,
	"Manivannan Sadhasivam" <manivannan.sadhasivam@linaro.org>,
	"Thomas Gleixner" <tglx@linutronix.de>,
	"Jason Cooper" <jason@lakedaemon.net>,
	"Andreas Färber" <afaerber@suse.de>,
	parthiban@linumiz.com, "Saravanan Sekar" <sravanhome@gmail.com>,
	linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-actions@lists.infradead.org,
	"Parthiban Nallathambi" <pn@denx.de>
Subject: Re: [PATCH v6 2/3] irqchip: Add Actions Semi Owl SIRQ controller
Date: Mon, 14 Sep 2020 11:51:54 +0300	[thread overview]
Message-ID: <20200914085154.GA8474@BV030612LT> (raw)
In-Reply-To: <b9053e939dea2b67ba9804aec1a110f5@kernel.org>

On Mon, Sep 14, 2020 at 09:07:18AM +0100, Marc Zyngier wrote:
> Cristian,
> 
> On 2020-09-14 08:02, Cristian Ciocaltea wrote:
> > Hi Marc,
> > 
> > On Fri, Sep 11, 2020 at 05:22:41PM +0100, Marc Zyngier wrote:
> > > On 2020-09-08 09:20, Cristian Ciocaltea wrote:
> > > > This interrupt controller is found in the Actions Semi Owl SoCs (S500,
> > > > S700 and S900) and provides support for handling up to 3 external
> > > > interrupt lines.
> > > >
> > > > Each line can be independently configured as interrupt and triggers on
> > > > either of the edges or either of the levels. Additionally, each line
> > > > can also be masked individually.
> > > >
> > > > The patch is based on the work started by Parthiban Nallathambi:
> > > > https://lore.kernel.org/lkml/20181126100356.2840578-1-pn@denx.de/
> > > >
> > > > Signed-off-by: Parthiban Nallathambi <pn@denx.de>
> > > > Signed-off-by: Saravanan Sekar <sravanhome@gmail.com>
> > > > [cristi: optimized DT, various fixes/cleanups/improvements]
> > > > Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
> > > 
> > > Who is the author of these patches? If this is a co-development,
> > > please
> > > use the relevant tags. Otherwise, the author of the patch must come as
> > > the first SoB.
> > 
> > I took the authorship for the driver patch, as mentioned in the cover
> > letter. So, if I understand correctly, my SoB should be moved on top and
> > I assume I also need to drop the related comment line.
> 
> Not quite. Please look at Documentation/process/submitting-patches.rst.

Yes, I have read it, but most probably I missed the information that
clarifies this authorship change handling.

> If Parthiban and Saravanan haven't authored anything in this patch,
> then drop them from the SoB list.

Sorry I haven't properly explained this before!

Their contributions to the driver code stopped in 2018, when v3 of the
patch series has been submitted.

> If they have contributed to the
> patch (which I expect), then their SoB must be preceded by their own
> Co-developed-by: tag.

Starting with v4, the work has been done exclusively by myself.

> To sum it up, it probably should look like:
> 
> Co-developed-by: Parthiban Nallathambi <pn@denx.de>
> Signed-off-by: Parthiban Nallathambi <pn@denx.de>
> Co-developed-by: Saravanan Sekar <sravanhome@gmail.com>
> Signed-off-by: Saravanan Sekar <sravanhome@gmail.com>
> Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
> 
> This is of course an assumption, and you should check it with the
> individuals above.

I have recently contacted Parthiban and he agreed that I can take the
authorship. So I should proceed with the 1st approach?

> Thanks,
> 
>         M.
> -- 
> Jazz is not dead. It just smells funny...

Thanks,
Cristi

  reply	other threads:[~2020-09-14  8:52 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-08  8:20 [PATCH v6 0/3] Add Actions Semi Owl family sirq support Cristian Ciocaltea
2020-09-08  8:20 ` [PATCH v6 1/3] dt-bindings: interrupt-controller: Add Actions SIRQ controller binding Cristian Ciocaltea
2020-09-08  8:20 ` [PATCH v6 2/3] irqchip: Add Actions Semi Owl SIRQ controller Cristian Ciocaltea
2020-09-11 16:22   ` Marc Zyngier
2020-09-14  7:02     ` Cristian Ciocaltea
2020-09-14  8:07       ` Marc Zyngier
2020-09-14  8:51         ` Cristian Ciocaltea [this message]
2020-09-14  9:19           ` Marc Zyngier
2020-09-14  9:40             ` Cristian Ciocaltea
2020-09-08  8:20 ` [PATCH v6 3/3] MAINTAINERS: Add entries for " Cristian Ciocaltea

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=20200914085154.GA8474@BV030612LT \
    --to=cristian.ciocaltea@gmail.com \
    --cc=afaerber@suse.de \
    --cc=devicetree@vger.kernel.org \
    --cc=jason@lakedaemon.net \
    --cc=linux-actions@lists.infradead.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=manivannan.sadhasivam@linaro.org \
    --cc=maz@kernel.org \
    --cc=parthiban@linumiz.com \
    --cc=pn@denx.de \
    --cc=robh+dt@kernel.org \
    --cc=sravanhome@gmail.com \
    --cc=tglx@linutronix.de \
    /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