All of lore.kernel.org
 help / color / mirror / Atom feed
From: mathieu.desnoyers at efficios.com (Mathieu Desnoyers)
Subject: [PATCH] selftest/rseq: Remove duplicate header
Date: Mon, 4 Mar 2019 14:57:47 -0500 (EST)	[thread overview]
Message-ID: <712691085.1137.1551729467392.JavaMail.zimbra@efficios.com> (raw)
In-Reply-To: <CAFqt6zarwg3NnkbNYKEO-jrdHUw8GwMqUrLDTqgQV3D1dux-qQ@mail.gmail.com>

----- On Mar 4, 2019, at 1:53 PM, Souptick Joarder jrdr.linux at gmail.com wrote:

> On Tue, Mar 5, 2019 at 12:20 AM Peter Zijlstra <peterz at infradead.org> wrote:
>>
>> On Tue, Mar 05, 2019 at 12:08:27AM +0530, Souptick Joarder wrote:
>> > Remove duplicate header which is included twice
>> >
>> > Signed-off-by: Sabyasachi Gupta <sabyasachi.linux at gmail.com>
>> > Signed-off-by: Souptick Joarder <jrdr.linux at gmail.com>
>>
>> That SoB chain is invalid.
> 
> I didn't get why it is invalid ?

I think it's about having the author of the patch (From) as first
Signed-off-by, and then apply following Signed-off-by by maintainers
who pick up the patch. (That's what I am used to see)

What is the intent behind the second Signed-off-by by Sabyasachi Gupta ?

Thanks,

Mathieu

-- 
Mathieu Desnoyers
EfficiOS Inc.
http://www.efficios.com

WARNING: multiple messages have this Message-ID (diff)
From: mathieu.desnoyers@efficios.com (Mathieu Desnoyers)
Subject: [PATCH] selftest/rseq: Remove duplicate header
Date: Mon, 4 Mar 2019 14:57:47 -0500 (EST)	[thread overview]
Message-ID: <712691085.1137.1551729467392.JavaMail.zimbra@efficios.com> (raw)
Message-ID: <20190304195747.ZD8_EF8tE6jNS0q4STxanetY0z55z2gF2jpH7j-8eEQ@z> (raw)
In-Reply-To: <CAFqt6zarwg3NnkbNYKEO-jrdHUw8GwMqUrLDTqgQV3D1dux-qQ@mail.gmail.com>

----- On Mar 4, 2019,@1:53 PM, Souptick Joarder jrdr.linux@gmail.com wrote:

> On Tue, Mar 5, 2019@12:20 AM Peter Zijlstra <peterz@infradead.org> wrote:
>>
>> On Tue, Mar 05, 2019@12:08:27AM +0530, Souptick Joarder wrote:
>> > Remove duplicate header which is included twice
>> >
>> > Signed-off-by: Sabyasachi Gupta <sabyasachi.linux at gmail.com>
>> > Signed-off-by: Souptick Joarder <jrdr.linux at gmail.com>
>>
>> That SoB chain is invalid.
> 
> I didn't get why it is invalid ?

I think it's about having the author of the patch (From) as first
Signed-off-by, and then apply following Signed-off-by by maintainers
who pick up the patch. (That's what I am used to see)

What is the intent behind the second Signed-off-by by Sabyasachi Gupta ?

Thanks,

Mathieu

-- 
Mathieu Desnoyers
EfficiOS Inc.
http://www.efficios.com

WARNING: multiple messages have this Message-ID (diff)
From: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
To: Souptick Joarder <jrdr.linux@gmail.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
	paulmck <paulmck@linux.ibm.com>,
	Boqun Feng <boqun.feng@gmail.com>, shuah <shuah@kernel.org>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	linux-kselftest <linux-kselftest@vger.kernel.org>
Subject: Re: [PATCH] selftest/rseq: Remove duplicate header
Date: Mon, 4 Mar 2019 14:57:47 -0500 (EST)	[thread overview]
Message-ID: <712691085.1137.1551729467392.JavaMail.zimbra@efficios.com> (raw)
In-Reply-To: <CAFqt6zarwg3NnkbNYKEO-jrdHUw8GwMqUrLDTqgQV3D1dux-qQ@mail.gmail.com>

----- On Mar 4, 2019, at 1:53 PM, Souptick Joarder jrdr.linux@gmail.com wrote:

> On Tue, Mar 5, 2019 at 12:20 AM Peter Zijlstra <peterz@infradead.org> wrote:
>>
>> On Tue, Mar 05, 2019 at 12:08:27AM +0530, Souptick Joarder wrote:
>> > Remove duplicate header which is included twice
>> >
>> > Signed-off-by: Sabyasachi Gupta <sabyasachi.linux@gmail.com>
>> > Signed-off-by: Souptick Joarder <jrdr.linux@gmail.com>
>>
>> That SoB chain is invalid.
> 
> I didn't get why it is invalid ?

I think it's about having the author of the patch (From) as first
Signed-off-by, and then apply following Signed-off-by by maintainers
who pick up the patch. (That's what I am used to see)

What is the intent behind the second Signed-off-by by Sabyasachi Gupta ?

Thanks,

Mathieu

-- 
Mathieu Desnoyers
EfficiOS Inc.
http://www.efficios.com

  reply	other threads:[~2019-03-04 19:57 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-04 18:38 [PATCH] selftest/rseq: Remove duplicate header jrdr.linux
2019-03-04 18:38 ` Souptick Joarder
2019-03-04 18:38 ` Souptick Joarder
2019-03-04 18:36 ` mathieu.desnoyers
2019-03-04 18:36   ` Mathieu Desnoyers
2019-03-04 18:36   ` Mathieu Desnoyers
2019-03-04 18:49 ` peterz
2019-03-04 18:49   ` Peter Zijlstra
2019-03-04 18:49   ` Peter Zijlstra
2019-03-04 18:53   ` jrdr.linux
2019-03-04 18:53     ` Souptick Joarder
2019-03-04 18:53     ` Souptick Joarder
2019-03-04 19:57     ` mathieu.desnoyers [this message]
2019-03-04 19:57       ` Mathieu Desnoyers
2019-03-04 19:57       ` Mathieu Desnoyers
2019-03-05  6:37       ` jrdr.linux
2019-03-05  6:37         ` Souptick Joarder
2019-03-05  6:37         ` Souptick Joarder

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=712691085.1137.1551729467392.JavaMail.zimbra@efficios.com \
    --to=unknown@example.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.