Hi Peter, > initializer for the 'handled' variable. I amended the previously > posted fixup and was just about to send you the pull request when > you started to add patches to i2c/for-next. Oh, sorry! I wasn't sure if we agreed that you send pull-requests for v4.11 already or starting with v4.12. And since there seems to be no rc8 for 4.11 I decided to start pulling in. > probably not happen (anytime soon). I'm going to short out the wait > and just send a reworked pull request. See below. Perfect! > A few thing to take away from this. Phil didn't post the series to > LKML, and the kbuild bots didn't find the series until I added it to > my i2c-mux tree. Fengguang indicated that the kbuild bot will now > (or soon) start to track the i2c list, which might be good to know. Well, I asked Fengguang to remove the i2c list from that feature a while ago. People send out RFCs, debug patches, etc... and for all those build bot reports are just noise IMO. Build testing plus sparse+smatch testing for the patches when I apply them to my tree and then having my branches additionally checked by build bot works well for me. I will happily share my super-simple 'ninja-check' script with you which runs various code checkers when compiling. It is basically adding "W=1 C=1 CHECK='ninja-check'" to the kernel build command-line. I hope you are open for this workflow. But we can discuss, of course. > submission. So, from now on I think I'm just going to change my > acks to some message saying that the patch(es) have been added > to i2c-mux/for-next (in case the submission is clear-cut i2c-mux > and not at all about i2c-the-rest). If I just ack a submission I'll > expect you to pick it up. Ok? Perfect! > The question then becomes at approximately which point you'll need > a pull request? Or should you perhaps be pulling in my tree > on a more continuous level so that everything i2c-related is > available in one tree (i.e. your tree)? I prefer pull requests a little bit. Then, I get a consistent state approved by you and already checked by build bot. BTW is your tree in linux-next as well? > sign-off when you pull? It's not a big thing, but all things being > equal, I'd prefer the commits to stay as-is... Sure thing. It might have been done automatically, will check and fix my scripts... > > Cheers, > peda > > The following changes since commit 7a308bb3016f57e5be11a677d15b821536419d36: > > Linux 4.10-rc5 (2017-01-22 12:54:15 -0800) > > 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 f2114795f721bd5028284ddf84b150798a9b7a73: > > i2c: mux: pca954x: Add interrupt controller support (2017-02-10 08:23:51 +0100) And pulled! Thank you for the work! Wolfram
Attachment:
signature.asc
Description: PGP signature
