linux-kernel - Re: linux-next: build warning after merge of the tip tree

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 for Android: free password hash cracker in your pocket

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

Date:	Sat, 31 Aug 2013 08:41:10 +0200
From:	Ingo Molnar <mingo@...nel.org>
To:	Andi Kleen <ak@...ux.intel.com>
Cc:	Stephen Rothwell <sfr@...b.auug.org.au>,
	Andi Kleen <andi@...stfloor.org>,
	Thomas Gleixner <tglx@...utronix.de>,
	Ingo Molnar <mingo@...e.hu>, "H. Peter Anvin" <hpa@...or.com>,
	Peter Zijlstra <peterz@...radead.org>,
	linux-next@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: linux-next: build warning after merge of the tip tree

* Andi Kleen <ak@...ux.intel.com> wrote:

> > > I've seen this pattern of deficient changelogs a dozen 
> > > times in your patches this year alone ...
> > 
> > Ping?
> 
> I've re-sent the patch already last week.

hpa was on vacation, if he doesn't pick it up I'll apply it.

> Some perf patches are also pending, there just seems to be a long 
> backlog.
> 
> http://permalink.gmane.org/gmane.linux.kernel/1548787 
> http://permalink.gmane.org/gmane.linux.kernel/1548788 
> http://permalink.gmane.org/gmane.linux.kernel/1548790 
> http://permalink.gmane.org/gmane.linux.kernel/1548791

There's no perf patches backlog. The ones you link to here were delayed 
because you (again) ignored maintainer review feedback:

  https://lkml.org/lkml/2013/8/30/370

Not sure you noticed, but kernel subsystem maintainers are not your 
repeat-everything-a-thousand-times patch submission QA machinery.

I have no problems explaining kernel contribution basics to newbies, but 
as a long-time kernel contributor you are expected to submit patch series 
whose quality is proportional to the amount of time you have already spent 
submitting patches. I.e. the longer the time you actively spent sending 
patches, the higher quality your patch series should become.

Instead what I see from you are the same problems over and over again: 
sloppy patches, ignored review feedback.

So to protect other people's higher quality patch flows maintainers that 
deal with you frequently often have to put your faulty submissions to the 
tail of their TODO list, until you show more reliable patterns of 
behavior. I will eventually have to stop taking patches from you 
permanently, if your abuse of review feedback continues.

Instead of complaining and blaming the maintainer you should increase the 
quality of your patch submissions instead.

Thanks,

	Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/