linux-kernel - Re: [PATCH] i2c: at91: fix TXRDY interrupt spam

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] [day] [month] [year] [list]

Message-ID: <20190419182933.24pdqa73iu7wz74c@ninjato>
Date:   Fri, 19 Apr 2019 20:29:33 +0200
From:   Wolfram Sang <wsa@...-dreams.de>
To:     Raag Jadav <raag.jadav@...fochips.com>
Cc:     Ludovic Desroches <ludovic.desroches@...rochip.com>,
        Nicolas Ferre <nicolas.ferre@...rochip.com>,
        Alexandre Belloni <alexandre.belloni@...tlin.com>,
        "linux-i2c@...r.kernel.org" <linux-i2c@...r.kernel.org>,
        "linux-arm-kernel@...ts.infradead.org" 
        <linux-arm-kernel@...ts.infradead.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] i2c: at91: fix TXRDY interrupt spam


> *************************************************************************************************************************************************************
> eInfochips Business Disclaimer: This e-mail message and all
> attachments transmitted with it are intended solely for the use of the
> addressee and may contain legally privileged and confidential
> information. If the reader of this message is not the intended
> recipient, or an employee or agent responsible for delivering this
> message to the intended recipient, you are hereby notified that any
> dissemination, distribution, copying, or other use of this message or
> its attachments is strictly prohibited. If you have received this
> message in error, please notify the sender immediately by replying to
> this message and please delete it from your computer. Any views
> expressed in this message are those of the individual sender unless
> otherwise stated. Company has taken enough precautions to prevent the
> spread of viruses. However the company accepts no liability for any
> damage caused by any virus transmitted by this email.
> *************************************************************************************************************************************************************

Your patch might be correct, but as a general rule we do not accept it
with a disclaimer like this. I mean we spread your patch all over the
world if it is accepted :) Could you ask your company to drop the
disclaimer when employees communicate with free software projects? Or if
it is OK with them if you use another email address?

Oh, and your mail had no To: header, please use the i2c-list next time.


Download attachment "signature.asc" of type "application/pgp-signature" (834 bytes)