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]
Message-ID: <20111214004807.GB8961@kroah.com>
Date:	Tue, 13 Dec 2011 16:48:07 -0800
From:	Greg KH <greg@...ah.com>
To:	Ravishankar karkala Mallikarjunayya 
	<ravishankar.km@...enturtles.in>
Cc:	gregkh@...e.de, wfp5p@...ginia.edu, devel@...verdev.osuosl.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 29/29] Staging: comedi: fix printk issue in
 contec_pci_dio.c

On Mon, Dec 12, 2011 at 10:49:41AM +0530, Ravishankar karkala Mallikarjunayya wrote:
> This is a patch to the contec_pci_dio.c file that fixes up a
> printk warning found by the checkpatch.pl tool.
> 
> Converted printks to dev_<levels> and Removed unnecessary
> printk statements.

You forgot to add to the changelog entry this text:

	Breaks the build.

which would have saved me a lot of time tracking down the patch in this
series that was causing problems.

{sigh}

Your next patch series better come with perfectly spelled changelog
entries that actually describe what the patches do, numbered properly
(none of this 30/30 crap after a 00/29 series), not break the build (is
that asking too much?) apply with no fuzz, and to help it all out, a
home made holiday bread of your choosing, as long as it's fresh, and
does not contain dried fruit bits (soaked in liquor can't hurt either.)

Otherwise I'm very tempted to just add you to my kill file, it would
save me lots of time and frustration, and likewise, I'm sure yours as
well.

Get baking,

greg k-h
--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ