netdev - Re: [PATCH net-next ] cxgb4: Fix issues caught by sparse in dcb patchset

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 23 Jun 2014 22:26:32 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	anish@...lsio.com
Cc:	netdev@...r.kernel.org, leedom@...lsio.com, hariprasad@...lsio.com
Subject: Re: [PATCH net-next ] cxgb4: Fix issues caught by sparse in dcb
 patchset

From: Anish Bhatt <anish@...lsio.com>
Date: Mon, 23 Jun 2014 17:27:28 -0700

> Hi,
>    This patch fixes warnings generated by sparse as pointed out by kbuild test robot, please appy to net-next. Applies on top of commit 79631c89ed70643fd0579a65834b227795b251ee
> Thanks,
> Anish
> 
> Signed-off-by: Anish Bhatt <anish@...lsio.com>

Please resubmit this properly.

First of all, the subject in the patch is not the place to mention
the SHA1 ID of the commit that added the problem.

Instead you should mention it in the commit message body and
you cannot provide just the SHA1 ID, you must also provide
the header line text of the commit right afterwards inside
of parenthesis and double quotes, for example like this:

	$(SHA1_ID) ("cxgb4: blah blah blah")

Since this is a one patch series, this header posting is not really
necessary, put that material into the patch commit message itself
and just post that.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html