Re: [PATCH 1/2] Kconfig: Allow disabling of CONFIG_DEVPORT

From: Ted Ts'o
Date: Sat Jul 16 2011 - 09:06:17 EST

On Sat, Jul 16, 2011 at 09:56:00AM +0200, Greg KH wrote:
> If you want to propose, and document, using "Company-bug-id", that's
> great, and is valid, but don't try to slip things in like this, with a
> company specific name, into the standardized tag area and claim it is
> acceptable after the fact.
> Again, I think people here are somehow forgetting the 300+ different
> companies that contribute to the kernel...

I've been doing this for several years, and there have been times when
I've put in Bugzilla references to both RedHat *and* SuSE bugs that
were closed due to customer confidential information. I had access
because of NDA's signed between IBM and the enterprise distro's, and
the release engineers at both distro's seemed to be happy that I did
this. In some cases I didn't have access to the bugzilla entry in
question, but I added the reference out of courtesy to the help desk
folks at the distro in question so they could more easily track the
fix as it travelled upstream to Linus and to various other derivitive
kernels, including the stable kernel series.

This is not new. I've tended not to put it in the signed-off-block,
so when I've done it it's just been part of the commit description.

If it eases friction to some subset of the people who are using the
kernel, especially to people who helped me debug a problem in ext3,
ext4, e2fsprogs, etc., it seems like it's just common courtesy to
include a single line so the bugfix can be more easily tracked. If
they helped me, I should help them.

I certainly don't plan to change this for anything for which I'm the
maintainer, and I would encourage other maintainers to do the same.

- Ted

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at
Please read the FAQ at