From: Patrick McHardy <kaber@trash.net>
To: Ingo Molnar <mingo@elte.hu>
Cc: Herbert Xu <herbert@gondor.apana.org.au>,
"David S. Miller" <davem@davemloft.net>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Crypto Mailing List <linux-crypto@vger.kernel.org>
Subject: Re: [PATCH] crypto: fix error flow of crypto/testmgr.c:test_comp()
Date: Tue, 25 Nov 2008 18:26:56 +0100 [thread overview]
Message-ID: <492C3560.8030904@trash.net> (raw)
In-Reply-To: <20081125171438.GK22504@elte.hu>
Ingo Molnar wrote:
> btw, on a related note, there's a couple of networking related warning
> fixes/annotations i've got queued up.
>
> I've got 37 commits of that nature in the tip/warnings/* topic
> branches:
> [...]
>
> They are done mainly so that we can notice the warnings we introduce
> via any of the -tip trees - but we analyze and look at all other types
> of upstream kernel warnings as well.
>
> I'll thus keep these commits indefinitely - but if someone from the
> networking side would like to work with us to pick them up and
> eventually nurse them upstream, that would be great!
>
> One thing is not really feasible: there's just too many of them for me
> to spend 10 minutes on each to submit them with a proper Cc:, etc.
> (such overhead mounts up quickly if you do the numbers)
>
> So i've attached them below as a dump of patches. If someone wants to
> cherry-pick bits of them, they are also available in
> tip/auto-warnings-next:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/tip/linux-2.6-tip.git auto-warnings-next
>
> Warning: some of them might be bad, so please double check the
> analysis.
> commit c390a3784564c1fb2183e4a31ea39a9beb47d034
> Author: Ingo Molnar <mingo@elte.hu>
> Date: Tue Nov 25 11:31:28 2008 +0100
>
> fix warning in net/netfilter/nf_conntrack_ftp.c
I've picked up this one in my nf-next-2.6.git tree.
> commit decc1656e870c9e5bd94f2357b8496b8da6c2e73
> Author: Ingo Molnar <mingo@elte.hu>
> Date: Sat Oct 18 19:14:40 2008 +0200
>
> fix warning in net/netfilter/nf_conntrack_proto_sctp.c
This one is already fixed differently in my tree.
> commit b5a7c2b9e1a1b4d80da5d66b330545fdeafe1dad
> Author: Ingo Molnar <mingo@elte.hu>
> Date: Fri Oct 17 19:48:51 2008 +0200
>
> fix warning in net/netfilter/nf_conntrack_proto_tcp.c
I've also picked up this one.
next prev parent reply other threads:[~2008-11-25 17:27 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-21 2:43 Crypto Update for 2.6.26 Herbert Xu
2008-07-14 12:14 ` Crypto Update for 2.6.27 Herbert Xu
2008-10-10 7:09 ` Crypto Update for 2.6.28 Herbert Xu
2008-10-10 18:22 ` Linus Torvalds
2008-10-10 18:29 ` Randy Dunlap
2008-10-11 2:13 ` Herbert Xu
2008-11-25 8:58 ` [PATCH] crypto: fix error flow of crypto/testmgr.c:test_comp() Ingo Molnar
2008-11-25 15:20 ` Herbert Xu
2008-11-25 17:14 ` Ingo Molnar
2008-11-25 17:26 ` Patrick McHardy [this message]
2008-11-25 21:52 ` David Miller
2008-11-26 1:09 ` [warnings] 37 warning fixes in networking related files Ingo Molnar
2008-11-26 1:11 ` David Miller
2008-11-26 1:08 ` [PATCH] crypto: fix error flow of crypto/testmgr.c:test_comp() David Miller
2008-11-26 2:40 ` Ingo Molnar
2008-12-10 12:35 ` Crypto Update for 2.6.28 Herbert Xu
2008-12-24 22:20 ` Herbert Xu
2008-12-24 22:32 ` Linus Torvalds
2008-12-24 23:47 ` Herbert Xu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=492C3560.8030904@trash.net \
--to=kaber@trash.net \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox