public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: Vlad Zolotarov <vlad@scalemp.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
	"Shai Fultheim (Shai@ScaleMP.com)" <Shai@scalemp.com>,
	Ido Yariv <ido@wizery.com>
Subject: Re: [PATCH v3 1/2] x86: Define early read-mostly per-cpu macros
Date: Mon, 21 May 2012 14:28:59 +0200	[thread overview]
Message-ID: <20120521122859.GA17065@gmail.com> (raw)
In-Reply-To: <10387490.kMM6uuuW2C@vlad>


* Vlad Zolotarov <vlad@scalemp.com> wrote:

> On Monday, May 21, 2012 10:46:26 AM Ingo Molnar wrote:
> > * Vlad Zolotarov <vlad@scalemp.com> wrote:
> > > Some read-mostly per-cpu data may need to be declared or defined early,
> > > so it can be initialized and accessed before per_cpu areas are
> > > allocated.
> > > 
> > > Only the data that resides in the per_cpu areas should be read-mostly,
> > > as there is little benefit in optimizing cache lines on initialization.
> > > 
> > > Signed-off-by: Vlad Zolotarov <vlad@scalemp.com>
> > > Signed-off-by: Ido Yariv <ido@wizery.com>
> > > Signed-off-by: Shai Fultheim <shai@scalemp.com>
> > 
> > That's not a valid signoff chain. If you send me a patch then
> > you should be the last SOB - but as the author you should be the
> > first SOB as well. I edited the two SOBs to be Acked-by's.
> 
> Thanks, Ingo. I understand. However the "history" of this 
> patch is not as simple as u represent. ;)
> 
> It was originally written by Ido and I just posted it (then I 
> put my SOB at the end of SOB list). But after u noted that it 
> didn't compile on !SMP i reworked it but yet Ido did at least 
> half of the coding, so I put my SOB at the first place (as I 
> was the last one writing the code) and then Ido's as he 
> actually wrote the code in this patch as well and I do wanted 
> to give him a credit.

The proper way to do that is to add a "Originally-From: " tag, 
or to keep him as the author (and first SOB) and desccribe your 
own changes as comments between the SOBs:

 Signed-off-by: Original Author
 [ cleaned up the code a bit ]
 Signed-off-by: Second Author
 [ restructured it ]
 Signed-off-by: You

> Do u still think changing his (Ido's) SOB to Acked-by was the 
> right thing to do?

If they agree with it then you can send it to me that way - or 
the above way, or you can add any extra authors in a copyright 
notice - but the signoff chain should be a chain, with the 
primary author as the first SOB and the person sending me the 
patch being the last SOB.

Thanks,

	Ingo

  reply	other threads:[~2012-05-21 12:29 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-20 15:19 [PATCH v3 1/2] x86: Define early read-mostly per-cpu macros Vlad Zolotarov
2012-05-21  8:46 ` Ingo Molnar
2012-05-21 11:12   ` Vlad Zolotarov
2012-05-21 12:28     ` Ingo Molnar [this message]
2012-05-21 13:27       ` Vlad Zolotarov

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=20120521122859.GA17065@gmail.com \
    --to=mingo@kernel.org \
    --cc=Shai@scalemp.com \
    --cc=hpa@zytor.com \
    --cc=ido@wizery.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=tglx@linutronix.de \
    --cc=vlad@scalemp.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