[PULL REQUEST] i2c-mux for 4.14-rc1

[PULL REQUEST] i2c-mux for 4.14-rc1

[Peter Rosin]

Hi Wolfram,

In this cycle, we have the following:
- header-file reshuffle
- pinctrl driver simplification
and a couple of small maintenance changes.

Please pull.

Cheers,
peda

The following changes since commit aae4e7a8bc44722fe70d58920a36916b1043195e:

  Linux 4.13-rc4 (2017-08-06 18:44:49 -0700)

are available in the git repository at:

  https://github.com/peda-r/i2c-mux.git i2c-mux/for-next

for you to fetch changes up to fabf08a0cd63ce39287646ceea10ac34781418f4:

  i2c: mux: i2c-arb-gpio-challenge: allow compiling w/o OF support (2017-08-22 08:37:03 +0200)

----------------------------------------------------------------
Dan Carpenter (1):
      i2c: mux: pinctrl: potential NULL dereference on error

Peter Rosin (4):
      i2c: mux: pinctrl: remove platform_data
      i2c: mux: pinctrl: drop the idle_state member
      i2c: Documentation: i2c-topology: mention recent driver additions
      i2c: mux: i2c-arb-gpio-challenge: allow compiling w/o OF support

Wolfram Sang (3):
      i2c: mux: pca9541: sort include files
      i2c: mux: pca954x: move header file out of I2C realm
      i2c: mux: mlxcpld: move header file out of I2C realm

 Documentation/i2c/i2c-topology                     |   6 +
 drivers/i2c/muxes/Kconfig                          |   3 +-
 drivers/i2c/muxes/i2c-mux-mlxcpld.c                |   2 +-
 drivers/i2c/muxes/i2c-mux-pca9541.c                |   9 +-
 drivers/i2c/muxes/i2c-mux-pca954x.c                |   2 +-
 drivers/i2c/muxes/i2c-mux-pinctrl.c                | 225 +++++++--------------
 include/linux/i2c-mux-pinctrl.h                    |  41 ----
 include/linux/{i2c => platform_data}/pca954x.h     |   0
 include/linux/{i2c => platform_data/x86}/mlxcpld.h |   0
 9 files changed, 86 insertions(+), 202 deletions(-)
 delete mode 100644 include/linux/i2c-mux-pinctrl.h
 rename include/linux/{i2c => platform_data}/pca954x.h (100%)
 rename include/linux/{i2c => platform_data/x86}/mlxcpld.h (100%)

Re: [PULL REQUEST] i2c-mux for 4.14-rc1

[Wolfram Sang]

[-- Attachment #1: Type: text/plain, Size: 740 bytes --]

On Thu, Aug 24, 2017 at 09:00:27AM +0200, Peter Rosin wrote:
> Hi Wolfram,
> 
> In this cycle, we have the following:
> - header-file reshuffle
> - pinctrl driver simplification
> and a couple of small maintenance changes.
> 
> Please pull.
> 
> Cheers,
> peda
> 
> The following changes since commit aae4e7a8bc44722fe70d58920a36916b1043195e:
> 
>   Linux 4.13-rc4 (2017-08-06 18:44:49 -0700)
> 
> are available in the git repository at:
> 
>   https://github.com/peda-r/i2c-mux.git i2c-mux/for-next
> 
> for you to fetch changes up to fabf08a0cd63ce39287646ceea10ac34781418f4:
> 
>   i2c: mux: i2c-arb-gpio-challenge: allow compiling w/o OF support (2017-08-22 08:37:03 +0200)
> 

Applied to for-next, thanks!


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

Re: [PULL REQUEST] i2c-mux for 4.14-rc1

[Peter Rosin]

On 2017-08-27 15:27, Wolfram Sang wrote:
> On Thu, Aug 24, 2017 at 09:00:27AM +0200, Peter Rosin wrote:
>> Hi Wolfram,
>>
>> In this cycle, we have the following:
>> - header-file reshuffle
>> - pinctrl driver simplification
>> and a couple of small maintenance changes.
>>
>> Please pull.
>>
>> Cheers,
>> peda
>>
>> The following changes since commit aae4e7a8bc44722fe70d58920a36916b1043195e:
>>
>>   Linux 4.13-rc4 (2017-08-06 18:44:49 -0700)
>>
>> are available in the git repository at:
>>
>>   https://github.com/peda-r/i2c-mux.git i2c-mux/for-next
>>
>> for you to fetch changes up to fabf08a0cd63ce39287646ceea10ac34781418f4:
>>
>>   i2c: mux: i2c-arb-gpio-challenge: allow compiling w/o OF support (2017-08-22 08:37:03 +0200)
>>
> 
> Applied to for-next, thanks!

Hmm, it's not pushed out yet. No rush on my account, I'm probably just
impatient. But (just so that I have something to go on) what is the
ball-park time between your 'apply' message and the following push?

Cheers,
Peter

Re: [PULL REQUEST] i2c-mux for 4.14-rc1

[Wolfram Sang]

[-- Attachment #1: Type: text/plain, Size: 401 bytes --]


> Hmm, it's not pushed out yet. No rush on my account, I'm probably just
> impatient. But (just so that I have something to go on) what is the
> ball-park time between your 'apply' message and the following push?

Usually the same evening. This time it got delayed/interrupted because
patchwork was failing for me yesterday and so my workflow was a bit ...
unusual. But it is back to work now, yay!


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]