linux-kernel - Re: [PATCH 2/5] staging/vme: fix checkpatch warning

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: <20120817074644.GL4559@mwanda>
Date:	Fri, 17 Aug 2012 10:46:44 +0300
From:	Dan Carpenter <dan.carpenter@...cle.com>
To:	Toshiaki Yamane <yamanetoshi@...il.com>
Cc:	Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
	Martyn Welch <martyn.welch@...com>,
	Manohar Vanga <manohar.vanga@...il.com>,
	devel@...verdev.osuosl.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 2/5] staging/vme: fix checkpatch warning

You've got the same subject repeated 5 times.

It would be better to merge all the vme_user.c printk fixes into
one patch.
[patch 1/3] Staging: vme: Fix a white space issue
[patch 2/3] Staging: vme: Use pr_ printks in vme_user.c
[patch 3/3] Staging: vme: Use pr_ printks in vme_pio2_core.c

It's not a huge deal, it just seems like there was some confusion on
how to break patches up.

regards,
dan carpenter

--
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/