netdev - Re: [Patch net-next] net_sched: act: Dont increment refcnt on replace

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: <20131222.175015.561115381077901987.davem@davemloft.net>
Date:	Sun, 22 Dec 2013 17:50:15 -0500 (EST)
From:	David Miller <davem@...emloft.net>
To:	jhs@...atatu.com
Cc:	netdev@...r.kernel.org, xiyou.wangcong@...il.com,
	eric.dumazet@...il.com
Subject: Re: [Patch net-next] net_sched: act: Dont increment refcnt on
 replace

From: Jamal Hadi Salim <jhs@...atatu.com>
Date: Sun, 22 Dec 2013 07:35:39 -0500

> This bug seems to have been around for some time, nothing to do with
> recent changes; i am just doing tests i havent run in a while and
> saw it. It is against net-next. If you think it is important enough,
> I could also create one against linus tree..

Jamal, I've tried to be patient with you over the years, but I really
need you to start submitting your changes more cleanly.

Your SUBJECT line MUST be the first line of the commit log message,
optionally with a prefix of the form "[PATCH xxx]" where "xxx" can
be "net", "net-next" and also contain versioning information such
as "v2" or "v3" etc.

Then your email message body must contain the commit message, with
no indentation whatsoever.

Then you may optionally provide a line with "---" then supplementary
information and text which you don't wish to end up in the final
commit message.

Then you provide the patch.

And this all must be inline and not as an attachment.

What I get from you is the output of "git show" as an attachment and I
absolutely cannot use that as-is.  It idents the commit message,
amongst other things.

You can use "git format-patch" instead and munge it into a proper
email by hand.  Unlike "git show", "git format-patch" won't indent
the commit message.

Please take a few moments to read other netdev patch postings
and see how regulars do it.  They do what works for me.

Thank you.
--
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