From: Greg KH <gregkh@suse.de>
To: Theodore Tso <tytso@MIT.EDU>
Cc: Mike Waychison <mikew@google.com>,
Andrew Morton <akpm@linux-foundation.org>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
x86@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] Kconfig: Allow disabling of CONFIG_DEVPORT
Date: Fri, 15 Jul 2011 16:51:32 +0200 [thread overview]
Message-ID: <20110715145132.GA4296@suse.de> (raw)
In-Reply-To: <C70E3912-6AA9-4EB3-85CC-11BF90D230C8@mit.edu>
On Fri, Jul 15, 2011 at 09:13:27AM -0400, Theodore Tso wrote:
>
> On Jul 15, 2011, at 2:41 AM, Greg KH wrote:
>
> >
> > Ok, but what happens if all 2000+ different companies start adding their
> > fields to the signed-off-by: area of the kernel for their internal
> > tracking systems?
>
> That's been happening for a long time; there have been kernel patches
> referencing LTC, RHEL, and SLES bugzilla entries; many of those
> bug entries are not public so as not to reveal customer confidential
> information. I've never seen anyone complain about that before.
But none of them are on the Signed-off-by: line area, right?
Also, putting it in the text of the changelog, with a url, is fine. And
it had better be a public url, otherwise it makes no sense at all. I've
seen many public SUSE and Ubuntu urls in changelog entries, any
non-public ones should not be in there at all.
Just like with gerrit ids in signed-off-by areas, references to internal
bugzilla entries, in the signed-off-by area, should not be there at all.
greg k-h
next prev parent reply other threads:[~2011-07-15 14:51 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-14 20:34 [PATCH 1/2] Kconfig: Allow disabling of CONFIG_DEVPORT Mike Waychison
2011-07-14 20:34 ` [PATCH 2/2] x86: Allow disabling of sys_iopl, sys_ioperm Mike Waychison
2011-07-14 20:37 ` H. Peter Anvin
2011-07-14 20:38 ` Mike Waychison
2011-07-14 20:40 ` H. Peter Anvin
2011-07-18 14:35 ` Jiri Kosina
2011-07-14 22:31 ` Andrew Morton
2011-07-14 22:35 ` H. Peter Anvin
2011-07-14 22:40 ` Mike Waychison
2011-07-14 22:45 ` H. Peter Anvin
2011-07-14 23:03 ` Alan Cox
2011-07-14 23:04 ` Alan Cox
2011-07-20 19:42 ` Ingo Molnar
2011-07-14 22:42 ` Alan Cox
2011-07-14 22:48 ` Mike Waychison
2011-07-14 23:00 ` Alan Cox
2011-07-14 23:20 ` Mike Waychison
2011-07-14 23:39 ` Alan Cox
2011-07-15 0:48 ` Mike Waychison
2011-07-15 9:55 ` Alan Cox
2011-07-15 18:13 ` Mike Waychison
2011-07-15 18:14 ` H. Peter Anvin
2011-07-15 22:30 ` Andrew G. Morgan
2011-07-15 22:42 ` Mike Waychison
2011-07-17 23:19 ` Eric Paris
2011-07-18 0:04 ` H. Peter Anvin
2011-07-14 21:21 ` [PATCH 1/2] Kconfig: Allow disabling of CONFIG_DEVPORT Greg KH
2011-07-14 22:17 ` Mike Waychison
2011-07-15 6:41 ` Greg KH
2011-07-15 13:13 ` Theodore Tso
2011-07-15 14:51 ` Greg KH [this message]
2011-07-15 14:58 ` Alan Cox
2011-07-15 15:19 ` Greg KH
2011-07-15 16:45 ` Mike Waychison
2011-07-15 17:01 ` Greg KH
2011-07-15 17:51 ` Mike Waychison
2011-07-15 18:10 ` H. Peter Anvin
2011-07-15 18:50 ` Andrew Morton
2011-07-15 18:55 ` Ted Ts'o
2011-07-16 7:56 ` Greg KH
2011-07-16 13:05 ` Ted Ts'o
2011-07-16 16:38 ` Christoph Hellwig
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=20110715145132.GA4296@suse.de \
--to=gregkh@suse.de \
--cc=akpm@linux-foundation.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mikew@google.com \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=tytso@MIT.EDU \
--cc=x86@kernel.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