netdev - Re: [RFC] Documentation: add documentation for rc-series and merge window

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Fri, 19 Jun 2009 15:51:00 -0700
From:	"Luis R. Rodriguez" <lrodriguez@...eros.com>
To:	Pavel Machek <pavel@....cz>
Cc:	Jouni Malinen <j@...fi>,
	Luis Rodriguez <Luis.Rodriguez@...eros.com>,
	Greg KH <greg@...ah.com>, "corbet@....net" <corbet@....net>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"torvalds@...ux-foundation.org" <torvalds@...ux-foundation.org>,
	"akpm@...ux-foundation.org" <akpm@...ux-foundation.org>,
	"alan@...rguk.ukuu.org.uk" <alan@...rguk.ukuu.org.uk>,
	"linux-wireless@...r.kernel.org" <linux-wireless@...r.kernel.org>,
	"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
	"tshibata@...jp.nec.com" <tshibata@...jp.nec.com>
Subject: Re: [RFC] Documentation: add documentation for rc-series and merge 
	window

On Fri, Jun 19, 2009 at 3:19 PM, Pavel Machek<pavel@....cz> wrote:
>
>> >> +2.0.2: RC-SERIES RULES
>> >> +
>> >> +Rules on what kind of patches are accepted after the merge window closes.
>> >> +These are patches targeted for the kernel rc-series of a kernel prior
>> >> +to its release.
>> >> +
>> >> + - it must fix a reported regression
>> >> + - it must fix a reported security hole
>> >> + - it must fix a reported oops/kernel hang
>> >
>> > - it must fix a bug.
>>
>> Well that's for certain, but there is a difference between a general
>> notion of a bug and the type of bug fixes that should go in during the
>> rc-series. This documentation patch highlights the difference.
>
> Yes, and I'm trying to tell you that this documentation patch is
> wrong.

This mean you might be able to help correct this.

> Non-intrusive bugfixes _are_ welcome after -rc1.

That's great news to me.

I think it would really help to get a clarification on what is meant
by "non-intrusive bugfixes" though. Can you elaborate on that?

>> > Non-intrusive bugfixes too, afaict.
>>
>> It really depends on what you mean but generally no, and this is why I
>> think this clarification is important.
>
> I believe you are wrong.

I was actually hoping I would be. But I'd like some confirmation that I am.

For example, based on your feedback we have a series of fixes we'd
like to try to get merged for 2.6.31-rc2 for ath9k. I have been under
the impression that since those fixes do not meet the criteria
clarified by my original patch on documentation for the rc-series that
they would not get merged and our only option to get users to get
these patches is to wait for 2.6.32 or use some sort of bleeding edge
backport package. We try hard to get out our patches in time prior to
the merge window but sometimes some patches don't manage hit that
timeline so if you tell me we can certainly send "non-intrusive bug
fixes" post rc1 then that is what we will try to do. I just do not
want to get bitch slapped about it when we do.

  Luis
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html