linux-kernel - Re: [ARM] Fix kernel compile error: drivers/crypto/ixp4xx

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]

Date:	Tue, 31 Dec 2013 18:14:27 +0000
From:	Russell King - ARM Linux <linux@....linux.org.uk>
To:	Gerhard Sittig <gsi@...x.de>
Cc:	Krzysztof Hałasa <khalasa@...p.pl>,
	lkml <linux-kernel@...r.kernel.org>,
	linux-arm-kernel@...ts.infradead.org,
	Christian Hohnstaedt <chohnstaedt@...ominate.com>,
	Herbert Xu <herbert@...dor.apana.org.au>
Subject: Re: [ARM] Fix kernel compile error: drivers/crypto/ixp4xx_crypto.c.

Please get rid of your Mail-Followup-To: header:

Mail-Followup-To: Krzysztof Hałasa <khalasa@...p.pl>,                           
        lkml <linux-kernel@...r.kernel.org>,                                    
        linux-arm-kernel@...ts.infradead.org,                                   
        Russell King <rmk+kernel@....linux.org.uk>,                             
        Christian Hohnstaedt <chohnstaedt@...ominate.com>,                      
        Herbert Xu <herbert@...dor.apana.org.au>                                
User-Agent: Mutt/1.5.21 (2010-09-15)                                            

It causes all recipients following the thread to be moved into the To:
header when someone replies to one of your messages, which is deemed to
be anti-social.  You can kill this header by adding:

	set followup_to=no

to your .muttrc file.

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