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] [day] [month] [year] [list]

Message-ID: <20090621062458.GC1474@ucw.cz>
Date:	Sun, 21 Jun 2009 08:24:58 +0200
From:	Pavel Machek <pavel@....cz>
To:	"Luis R. Rodriguez" <lrodriguez@...eros.com>
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

> > 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?

Typo fix in printk() is non-intrusive, 'apply this series' is
borderline; if issue is bad enough it may be ok. I guess only Linus
can clarify more.

> >> > 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

I believe 'no git merges after rc1' is one of rules.
									Pavel

-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
--
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