Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758248AbbBEQ5m (ORCPT ); Thu, 5 Feb 2015 11:57:42 -0500 Received: from mail-we0-f172.google.com ([74.125.82.172]:39428 "EHLO mail-we0-f172.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753953AbbBEQ5k (ORCPT ); Thu, 5 Feb 2015 11:57:40 -0500 MIME-Version: 1.0 In-Reply-To: <20150205163053.GQ29656@ZenIV.linux.org.uk> References: <1422884203-27173-1-git-send-email-rupran@einserver.de> <20150202141606.GY29656@ZenIV.linux.org.uk> <54CFCC46.40909@einserver.de> <20150205163053.GQ29656@ZenIV.linux.org.uk> From: "Lad, Prabhakar" Date: Thu, 5 Feb 2015 16:57:09 +0000 Message-ID: Subject: Re: use of opaque subject lines To: Al Viro Cc: Andreas Ruprecht , Oleg Drokin , Andreas Dilger , Greg Kroah-Hartman , HPDD-discuss@ml01.01.org, OSUOSL Drivers , LKML 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: 2288 Lines: 48 On Thu, Feb 5, 2015 at 4:30 PM, Al Viro wrote: > On Mon, Feb 02, 2015 at 08:13:10PM +0100, Andreas Ruprecht wrote: > >> On a serious note: I do understand what you're getting at, I don't take >> that personally (and I will send a v2 addressing the things above), but >> honestly, this kind of answer might just be a real turn-off for other >> people trying to get into kernel development... >> >> I don't want to start a whole new 'attitude in the kernel community' >> discussion, but I can't just let this go like that, sorry. > > Just during the last 12 hours or so, I've seen the following l-k traffic: > > Subject: [PATCH] usb: host/sl811-hcd: fix sparse warning > Subject: [PATCH] usb: gadget: function/f_sourcesink: fix sparse warning > Subject: [PATCH] tty: vt/vt: fix sparse warning > Subject: [PATCH] scsi: fix sparse warnings > Subject: [PATCH] bfa: bfa_core: fix sparse warning > Subject: [PATCH] scsi: fix sparse warning > Subject: [PATCH] xen/acpi-processor: fix sparse warning > Subject: [PATCH] scsi: initio: fix sparse warnings > Subject: [PATCH] scsi: dc395x: fix sparse warning > Subject: [PATCH] scsi: eata: fix sparse warning > Subject: [PATCH] scsi: qla1280: fix sparse warnings > Subject: [PATCH] scsi: ips: fix sparse warnings > Subject: [PATCH] fbdev: via/via_clock: fix sparse warning > Subject: [PATCH] usb: gadget: fix sparse warnings > Subject: [PATCH] usb: gadget: fix sparse warnings > Subject: [PATCH] usb: gadget: function/uvc_v4l2.c: fix sparse warnings > Subject: [PATCH] xen-netback: fix sparse warning > Subject: [PATCH] thermal: int340x: fix sparse warning > Subject: [PATCH] vxge: fix sparse warning > Subject: Re: [PATCH] xen-netback: fix sparse warning > Subject: [PATCH] ixgbe: fix sparse warnings > Subject: [PATCH] samsung-laptop: fix sparse warning > Subject: [PATCH] x86: thinkpad_acpi.c: fix sparse warning > Subject: [PATCH] Sony-laptop: fix sparse warning > all right I have stopped the script to send any more patches fixing sparse warnings ! Cheers, --Prabhakar Lad -- 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/