Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751642AbbGIIkG (ORCPT ); Thu, 9 Jul 2015 04:40:06 -0400 Received: from mail-ob0-f181.google.com ([209.85.214.181]:34665 "EHLO mail-ob0-f181.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751064AbbGIIj7 (ORCPT ); Thu, 9 Jul 2015 04:39:59 -0400 MIME-Version: 1.0 In-Reply-To: <20150708135402.GA13432@amd> References: <20150623064140.GA18300@kroah.com> <20150708135402.GA13432@amd> Date: Thu, 9 Jul 2015 10:39:58 +0200 X-Google-Sender-Auth: 37iwvHn3566pHb-yoZV7BJPl7uQ Message-ID: Subject: Re: kdbus: to merge or not to merge? From: Geert Uytterhoeven To: Pavel Machek Cc: Greg KH , Andy Lutomirski , Linus Torvalds , "linux-kernel@vger.kernel.org" , David Herrmann , Djalal Harouni , Havoc Pennington , "Eric W. Biederman" , One Thousand Gnomes , Tom Gundersen , Daniel Mack Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1103 Lines: 27 On Wed, Jul 8, 2015 at 3:54 PM, Pavel Machek wrote: > Apparently, new tools are needed in the community, as normal review > comments did not stop drivers/android/binder.c merge. > > For example binder_transaction does not exactly look like a kernel > code, "TODO: fput" does not really invoke confidence, and ammount of > BUG_ON()s is quite amazing... Amazingly, checkpatch (without --strict) only complains about long lines. Seems like the test for "BUG" is (and always has been) commented out... Gr{oetje,eeting}s, Geert -- Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org In personal conversations with technical people, I call myself a hacker. But when I'm talking to journalists I just say "programmer" or something like that. -- Linus Torvalds -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/