linux-kernel - Re: use of opaque subject lines

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:	Thu, 5 Feb 2015 16:57:09 +0000
From:	"Lad, Prabhakar" <prabhakar.csengg@...il.com>
To:	Al Viro <viro@...iv.linux.org.uk>
Cc:	Andreas Ruprecht <rupran@...server.de>,
	Oleg Drokin <oleg.drokin@...el.com>,
	Andreas Dilger <andreas.dilger@...el.com>,
	Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
	HPDD-discuss@...1.01.org,
	OSUOSL Drivers <devel@...verdev.osuosl.org>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: use of opaque subject lines

On Thu, Feb 5, 2015 at 4:30 PM, Al Viro <viro@...iv.linux.org.uk> 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@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/