linux-kernel - Re: [wsa:i2c/quirks 7/11] drivers/i2c/busses/i2c-axxia.c:452:27: sparse: symbol 'axxia_i2c_quirks' was not declared. Should it be static?

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

Message-ID: <20150109105712.GA1053@katana>
Date:	Fri, 9 Jan 2015 11:57:12 +0100
From:	Wolfram Sang <wsa@...-dreams.de>
To:	Fengguang Wu <fengguang.wu@...el.com>
Cc:	kbuild-all@...org, Anders Berg <anders.berg@...gotech.com>,
	linux-i2c@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [wsa:i2c/quirks 7/11] drivers/i2c/busses/i2c-axxia.c:452:27:
 sparse: symbol 'axxia_i2c_quirks' was not declared. Should it be static?

Hi Fengguang,

> It's normally private emails, except for the ones that carry patches
> with them. In which case public mailing lists will also be CCed.

OK, thought so.

> > Is there a way to achieve this? I know that adding "experimental" to the
> > branch name will skip the testing. Is there another pattern to prevent
> > sending mails to everyone?
> 
> I wonder if the occasional public emails are acceptable to you.

Not really. If I push out development code which is good enough to be
build tested but not ready to be sent upstream yet, I think other people
and mailing lists should not be bothered.

> not, it'd be trivial for me to add a list of "personal git trees"
> where all emails including the auto generated patches will be kept
> private (if commit author == committer).

For my workflow, everything except "for-current" and "for-next" should
be private. I do appreciate the patches for those two, so thanks for
that in general!

All the best,

   Wolfram


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