linux-kernel - [PATCH] Drop owner assignment from i2c

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

Date:	Fri, 10 Jul 2015 14:32:28 +0900
From:	Krzysztof Kozlowski <k.kozlowski@...sung.com>
To:	Corey Minyard <minyard@....org>, Peter Huewe <peterhuewe@....de>,
	Marcel Selhorst <tpmdd@...horst.net>,
	Jason Gunthorpe <jgunthorpe@...idianresearch.com>,
	Jarkko Sakkinen <jarkko.sakknen@...ux.intel.com>,
	Christophe Ricard <christophe.ricard@...il.com>,
	Krzysztof Kozlowski <k.kozlowski@...sung.com>,
	openipmi-developer@...ts.sourceforge.net,
	linux-kernel@...r.kernel.org, tpmdd-devel@...ts.sourceforge.net
Subject: [PATCH] Drop owner assignment from i2c_driver (and platform left-overs)

Hi,


The i2c drivers also do not have to set 'owner' field because
i2c_register_driver() will do it instead.

'owner' is removed from i2c drivers, which I was able to compile
with allyesconfig (arm, arm64, i386, x86_64, ppc64).
Only compile-tested.

The coccinelle script which generated the patch was sent here:
http://www.spinics.net/lists/kernel/msg2029903.html


Best regards,
Krzysztof

Krzysztof Kozlowski (1):
  char: Drop owner assignment from i2c_driver

 drivers/char/ipmi/ipmi_ssif.c       | 1 -
 drivers/char/tpm/st33zp24/i2c.c     | 1 -
 drivers/char/tpm/tpm_i2c_atmel.c    | 1 -
 drivers/char/tpm/tpm_i2c_infineon.c | 1 -
 drivers/char/tpm/tpm_i2c_nuvoton.c  | 1 -
 5 files changed, 5 deletions(-)

-- 
1.9.1

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