[RFC V2 04/12] i2c: opal: make use of the new infrastructure for quirks

[RFC V2 00/12] i2c: describe adapter quirks in a generic way · Wolfram Sang <hidden> · 2015-02-25
[RFC V2 03/12] i2c: at91: make use of the new infrastructure for quirks · Wolfram Sang <hidden> · 2015-02-25
Re: [RFC V2 03/12] i2c: at91: make use of the new infrastructure for quirks · Wolfram Sang <hidden> · 2015-03-08
Re: [RFC V2 03/12] i2c: at91: make use of the new infrastructure for quirks · Ludovic Desroches <hidden> · 2015-03-09
Re: [RFC V2 03/12] i2c: at91: make use of the new infrastructure for quirks · Ludovic Desroches <hidden> · 2015-03-10
Re: [RFC V2 03/12] i2c: at91: make use of the new infrastructure for quirks · Wolfram Sang <hidden> · 2015-03-12
[RFC V2 01/12] i2c: add quirk structure to describe adapter flaws · Wolfram Sang <hidden> · 2015-02-25
[RFC V2 02/12] i2c: add quirk checks to core · Wolfram Sang <hidden> · 2015-02-25
[RFC V2 05/12] i2c: qup: make use of the new infrastructure for quirks · Wolfram Sang <hidden> · 2015-02-25
[RFC V2 06/12] i2c: cpm: make use of the new infrastructure for quirks · Wolfram Sang <hidden> · 2015-02-25
[RFC V2 09/12] i2c: powermac: make use of the new infrastructure for quirks · Wolfram Sang <hidden> · 2015-02-25
[RFC V2 10/12] i2c: viperboard: make use of the new infrastructure for quirks · Wolfram Sang <hidden> · 2015-02-25
[RFC V2 12/12] i2c: bcm-iproc: make use of the new infrastructure for quirks · Wolfram Sang <hidden> · 2015-02-25
Re: [RFC V2 12/12] i2c: bcm-iproc: make use of the new infrastructure for quirks · Ray Jui <rjui@broadcom.com> · 2015-02-26
Re: [RFC V2 12/12] i2c: bcm-iproc: make use of the new infrastructure for quirks · Wolfram Sang <hidden> · 2015-03-12
[RFC V2 11/12] i2c: pmcmsp: make use of the new infrastructure for quirks · Wolfram Sang <hidden> · 2015-02-25
[RFC V2 08/12] i2c: dln2: make use of the new infrastructure for quirks · Wolfram Sang <hidden> · 2015-02-25
[RFC V2 07/12] i2c: axxia: make use of the new infrastructure for quirks · Wolfram Sang <hidden> · 2015-02-25
[RFC V2 04/12] i2c: opal: make use of the new infrastructure for quirks · Wolfram Sang <hidden> · 2015-02-25
Re: [RFC V2 04/12] i2c: opal: make use of the new infrastructure for quirks · Neelesh Gupta <hidden> · 2015-03-10
Re: [RFC V2 04/12] i2c: opal: make use of the new infrastructure for quirks · Benjamin Herrenschmidt <benh@kernel.crashing.org> · 2015-03-10
Re: [RFC V2 04/12] i2c: opal: make use of the new infrastructure for quirks · Neelesh Gupta <hidden> · 2015-03-11
Re: [RFC V2 04/12] i2c: opal: make use of the new infrastructure for quirks · Wolfram Sang <hidden> · 2015-03-12
Re: [RFC V2 00/12] i2c: describe adapter quirks in a generic way · Ivan T. Ivanov <hidden> · 2015-03-05
Re: [RFC V2 00/12] i2c: describe adapter quirks in a generic way · Wolfram Sang <hidden> · 2015-03-12
Re: [RFC V2 00/12] i2c: describe adapter quirks in a generic way · Wolfram Sang <hidden> · 2015-03-14

From: Wolfram Sang <hidden>
Date: 2015-03-12 14:55:05
Also in: linux-i2c, linux-mips, linuxppc-dev, lkml

I think we can't land up here by-passing the check for quirks so above
checks are duplicated here..

True.

So, as Ben seems OK with write-then-anything, can you send me your
changes as an incremental patch to mine with your Signed-off, please?

Thanks,

   Wolfram

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20150312/0817d7c0/attachment-0001.sig>

`h`	back out one level
`j`	next message in thread
`k`	previous message in thread
`l`	drill in
`Esc`	close help / fold thread tree
`?`	toggle this help