Message ID | 11adddb0-7484-cd3a-9978-30054741c089@axentia.se |
---|---|
State | Accepted |
Headers | show |
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!
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
> 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!