From: Ingo Molnar <mingo@elte.hu>
To: Ben Hutchings <ben@decadent.org.uk>
Cc: mingo@redhat.com, hpa@zytor.com, linux-kernel@vger.kernel.org,
a.p.zijlstra@chello.nl, tglx@linutronix.de,
linux-tip-commits@vger.kernel.org
Subject: Re: [tip:core/locking] lockdep, rtmutex, bug: Show taint flags on error
Date: Tue, 6 Dec 2011 18:54:43 +0100 [thread overview]
Message-ID: <20111206175443.GB25031@elte.hu> (raw)
In-Reply-To: <1323185640.7454.269.camel@deadeye>
* Ben Hutchings <ben@decadent.org.uk> wrote:
> On Tue, 2011-12-06 at 01:38 -0800, tip-bot for Ben Hutchings wrote:
> > Commit-ID: fbdc4b9a6c29befbcca65e5366e5aaf2abb7a013
> > Gitweb: http://git.kernel.org/tip/fbdc4b9a6c29befbcca65e5366e5aaf2abb7a013
> > Author: Ben Hutchings <ben@decadent.org.uk>
> > AuthorDate: Fri, 28 Oct 2011 04:36:55 +0100
> > Committer: Ingo Molnar <mingo@elte.hu>
> > CommitDate: Tue, 6 Dec 2011 08:16:49 +0100
> >
> > lockdep, rtmutex, bug: Show taint flags on error
> >
> > Show the taint flags in all lockdep and rtmutex-debug error messages.
> >
> > Signed-off-by: Ben Hutchings <ben@decadent.org.uk>
> > Signed-off-by: Peter Zijlstra <a.p.zijlstra@chello.nl>
> > Link: http://lkml.kernel.org/r/1319773015.6759.30.camel@deadeye
> > Signed-off-by: Ingo Molnar <mingo@elte.hu>
> [...]
>
> If you disagree with a patch, do not silently drop parts of
> it. I demand that you remove my 'Signed-off-by' as this is
> not the change I submitted.
FYI, there's no "I will only sign off on a patch doing two
things if it's applied in full" kind of condition in the SOB
definition, allowing that would break the GPL: people have the
right to take your modifications to the GPL-ed kernel and modify
it further.
Your original patch did two things. Peter did the sensible
thing: he split out the print_kernel_ident() changes from your
patch which stand on their own and kept your authorship in place
- that is what the above patch does.
Once you send it out the SOB is valid and people can (and
typically will) modify it - and if you are still the main author
(which you are here 100%) then keeping you as the author is the
proper approach - Peter added his own SOB after yours.
Thanks,
Ingo
next prev parent reply other threads:[~2011-12-06 17:56 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-28 3:36 [PATCH 1/2] lockdep,rtmutex,bug: " Ben Hutchings
2011-10-31 1:59 ` Rusty Russell
2011-11-16 21:52 ` Ben Hutchings
2011-11-16 22:24 ` Dave Jones
2011-11-17 8:48 ` Peter Zijlstra
2011-11-17 15:18 ` Ben Hutchings
2011-12-06 9:38 ` [tip:core/locking] lockdep, rtmutex, bug: " tip-bot for Ben Hutchings
2011-12-06 15:34 ` Ben Hutchings
2011-12-06 17:48 ` Peter Zijlstra
2011-12-06 17:55 ` Alan Cox
2011-12-06 17:56 ` Peter Zijlstra
2011-12-06 17:59 ` Ingo Molnar
2011-12-06 18:17 ` Ben Hutchings
2011-12-06 18:28 ` Ingo Molnar
2011-12-06 19:14 ` Ingo Molnar
2011-12-06 21:13 ` Ben Hutchings
2011-12-07 7:49 ` Ingo Molnar
2011-12-06 18:04 ` Ingo Molnar
2011-12-06 17:54 ` Ingo Molnar [this message]
2011-12-06 18:14 ` Nick Bowler
2011-12-06 18:20 ` Ingo Molnar
2011-12-06 18:21 ` Alan Cox
2011-12-06 18:34 ` Ingo Molnar
2011-12-06 18:23 ` Ben Hutchings
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=20111206175443.GB25031@elte.hu \
--to=mingo@elte.hu \
--cc=a.p.zijlstra@chello.nl \
--cc=ben@decadent.org.uk \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@redhat.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
all inboxes | Powered by JetHome®