linux-media.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Kaaira Gupta <kgupta@es.iitr.ac.in>
Cc: "Helen Koike" <helen.koike@collabora.com>,
	"Shuah Khan" <skhan@linuxfoundation.org>,
	"Mauro Carvalho Chehab" <mchehab@kernel.org>,
	linux-media@vger.kernel.org, linux-kernel@vger.kernel.org,
	"Kieran Bingham" <kieran.bingham@ideasonboard.com>,
	"Niklas Söderlund" <niklas.soderlund@ragnatech.se>
Subject: Re: [PATCH v2 0/3] media: vimc: Allow multiple capture devices to use the same sensor
Date: Fri, 31 Jul 2020 01:21:37 +0300	[thread overview]
Message-ID: <20200730222137.GF6107@pendragon.ideasonboard.com> (raw)
In-Reply-To: <20200730180949.GA14700@kaaira-HP-Pavilion-Notebook>

Hi Kaaira,

On Thu, Jul 30, 2020 at 11:39:49PM +0530, Kaaira Gupta wrote:
> On Thu, Jul 30, 2020 at 01:51:12PM +0300, Laurent Pinchart wrote:
> > On Fri, Jul 24, 2020 at 05:32:10PM +0530, Kaaira Gupta wrote:
> > > This is version 2 of the patch series posted by Niklas for allowing
> > > multiple streams in VIMC.
> > > The original series can be found here:
> > > https://patchwork.kernel.org/cover/10948831/
> > > 
> > > This series adds support for two (or more) capture devices to be 
> > > connected to the same sensors and run simultaneously. Each capture device 
> > > can be started and stopped independent of each other.
> > > 
> > > Patch 1/3 and 2/3 deals with solving the issues that arises once two 
> > > capture devices can be part of the same pipeline. While 3/3 allows for 
> > > two capture devices to be part of the same pipeline and thus allows for 
> > > simultaneously use.
> > 
> > I think this is really nice work, as it will make the vimc driver even
> > more useful for testing purposes.
> > 
> > I however just noticed that the patches seem to have lost Niklas'
> > authorship. Niklas posted v1 ([1]), and while there's absolutely no
> > issue with taking over a patch series (especially when the original
> > author is aware of that, and approves :-)), it's customary to keep the
> > original authorship.
> 
> Hm, I had a meeting with Kieren yesterday where he explained this to me.
> I wasn't aware of the distinction between authorship and a Signed-off
> tag, I thought signed-off implies authorship. Now that I know this, I
> will amend this in the next version I send.

No worries at all. The process is complicated :-)

> > Authorship, as recorded in the commit's "Author:" field (displayed by
> > "git show" or "git log" for instance), is distinct from Signed-off-by.
> > The original Signed-off-by line needs to be preserved to indicate the
> > original author's commitment to the certificate of origin ([2]), but in
> > itself that doesn't acknowledge original authorship of the code.
> > 
> > I'm sure this is an oversight. Authorship can easily be changed with the
> > --author option to "git commit --amend".
> > 
> > $ git show -s
> > commit 8be3a53e18e0e1a98f288f6c7f5e9da3adbe9c49 (HEAD -> tmp)
> > Merge: fc10807db5ce 3c597282887f
> > Author: Linus Torvalds <torvalds@linux-foundation.org>
> > Date:   Wed Jun 24 17:39:30 2020 -0700
> > 
> >     Merge tag 'erofs-for-5.8-rc3-fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/xiang/erofs
> > 
> >     Pull erofs fix from Gao Xiang:
> >      "Fix a regression which uses potential uninitialized high 32-bit value
> >       unexpectedly recently observed with specific compiler options"
> > 
> >     * tag 'erofs-for-5.8-rc3-fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/xiang/erofs:
> >       erofs: fix partially uninitialized misuse in z_erofs_onlinepage_fixup
> > $ git commit --amend --author 'Laurent Pinchart <laurent.pinchart@ideasonboard.com>'
> > [tmp 6a7191c2aee9] Merge tag 'erofs-for-5.8-rc3-fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/xiang/erofs
> >  Date: Wed Jun 24 17:39:30 2020 -0700
> > $ git show -s
> > commit 6a7191c2aee9e4a2ba375f14c821bc9b4d7f881b (HEAD -> tmp)
> > Merge: fc10807db5ce 3c597282887f
> > Author: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
> > Date:   Wed Jun 24 17:39:30 2020 -0700
> > 
> >     Merge tag 'erofs-for-5.8-rc3-fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/xiang/erofs
> >     
> >     Pull erofs fix from Gao Xiang:
> >      "Fix a regression which uses potential uninitialized high 32-bit value
> >       unexpectedly recently observed with specific compiler options"
> >     
> >     * tag 'erofs-for-5.8-rc3-fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/xiang/erofs:
> >       erofs: fix partially uninitialized misuse in z_erofs_onlinepage_fixup
> > 
> > Not that I would try to take ownership of a commit authored by Linus, I
> > doubt he would appreciate that :-)
> > 
> > Authorship is normally preserved through git-format-patch,
> > git-send-email and git-am:
> > 
> > - git-format-patch sets the "From:" line to the patch's author
> > 
> > - If the "From:" line is different than the mail sender, git-send-email
> >   replaces it with the sender's identity (as we don't want to forge
> >   e-mails with an incorrect sender). It then adds the original "From:"
> >   line *inside* the mail, just after the headers, right before the body
> >   of the commit message.
> > 
> > - git-am sets the author to the "From:" line from the e-mail's body if
> >   it exists, and uses the "From:" line from the e-mail's header (the
> >   sender's identity) otherwise.
> > 
> > If you use those tools authorship should get preserved automatically.
> > 
> > Of course new patches that you would add to the series should have your
> > authorship.
> > 
> > I hope this helps clarifying the process, please let me know if you have
> > any question.
> > 
> > [1] https://lore.kernel.org/linux-media/20190518010744.15195-1-niklas.soderlund+renesas@ragnatech.se/
> > [2] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/submitting-patches.rst#n431
> > 
> > > Changes since v1:
> > > 	- All three patches rebased on latest media-tree.
> > > 	Patch 3:
> > > 	- Search for an entity with a non-NULL pipe instead of searching
> > > 	  for sensor. This terminates the search at output itself.
> > > 
> > > Kaaira Gupta (3):
> > >   media: vimc: Add usage count to subdevices
> > >   media: vimc: Serialize vimc_streamer_s_stream()
> > >   media: vimc: Join pipeline if one already exists
> > > 
> > >  .../media/test-drivers/vimc/vimc-capture.c    | 35 ++++++++++++++++++-
> > >  .../media/test-drivers/vimc/vimc-debayer.c    |  8 +++++
> > >  drivers/media/test-drivers/vimc/vimc-scaler.c |  8 +++++
> > >  drivers/media/test-drivers/vimc/vimc-sensor.c |  9 ++++-
> > >  .../media/test-drivers/vimc/vimc-streamer.c   | 23 +++++++-----
> > >  5 files changed, 73 insertions(+), 10 deletions(-)

-- 
Regards,

Laurent Pinchart

      reply	other threads:[~2020-07-30 22:21 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-24 12:02 [PATCH v2 0/3] media: vimc: Allow multiple capture devices to use the same sensor Kaaira Gupta
2020-07-24 12:02 ` [PATCH v2 1/3] media: vimc: Add usage count to subdevices Kaaira Gupta
2020-07-24 12:02 ` [PATCH v2 2/3] media: vimc: Serialize vimc_streamer_s_stream() Kaaira Gupta
2020-07-24 12:02 ` [PATCH v2 3/3] media: vimc: Join pipeline if one already exists Kaaira Gupta
2020-07-28 12:24   ` Dafna Hirschfeld
2020-07-28 12:48     ` Kaaira Gupta
2020-07-29 10:58       ` Dafna Hirschfeld
2020-07-24 12:15 ` [PATCH v2 0/3] media: vimc: Allow multiple capture devices to use the same sensor Niklas Söderlund
2020-07-24 12:21   ` Kaaira Gupta
2020-07-27 14:31     ` Kieran Bingham
2020-07-27 17:54       ` Helen Koike
2020-07-28 11:39         ` Kaaira Gupta
2020-07-28 12:07           ` Dafna Hirschfeld
2020-07-28 14:00             ` Dafna Hirschfeld
2020-07-28 14:26               ` Kaaira Gupta
2020-07-29 13:05               ` Kieran Bingham
2020-07-29 13:16                 ` Dafna Hirschfeld
2020-07-29 13:27                   ` Kieran Bingham
2020-07-29 15:24                     ` Dafna Hirschfeld
2020-07-31 17:22                       ` Kaaira Gupta
2020-08-04 10:24                         ` Kieran Bingham
2020-08-04 18:49                           ` Kaaira Gupta
2020-08-04 18:52                             ` Kaaira Gupta
2020-08-05 15:18                       ` Helen Koike
2020-07-30 10:51 ` Laurent Pinchart
2020-07-30 18:09   ` Kaaira Gupta
2020-07-30 22:21     ` Laurent Pinchart [this message]

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=20200730222137.GF6107@pendragon.ideasonboard.com \
    --to=laurent.pinchart@ideasonboard.com \
    --cc=helen.koike@collabora.com \
    --cc=kgupta@es.iitr.ac.in \
    --cc=kieran.bingham@ideasonboard.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab@kernel.org \
    --cc=niklas.soderlund@ragnatech.se \
    --cc=skhan@linuxfoundation.org \
    /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 NNTP newsgroup(s).