Google
  Web www.spinics.net

5088/3: the SPI dependency

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]


Since we are over a week into the merge window, and I see no sign of
the SPI tree merging, it's time to make a decision on what to do about
the outstanding changes in my tree which depend on the SPI tree having
been merged first (iow, the presence of linux/spi/max7301.h.)

One solution is to continue twiddling my thumbs waiting for the SPI
tree to merge, which frankly is utterly boring and is just a waste of
my time.

Another solution is to back out the change, but that's extremely
painful to do because soo much other stuff relies on that commit.

Or we could commit a change on top of everything backing out the changes
to pcm027.c which require the SPI tree to merge first, and have the bits
which rely on max7301.h submitted later (which is, imho, what should've
happened.)

Or we could ignore the issue entirely and just merge the remaining
changes.

Unless I hear otherwise, I shall be intending to back out the troublesome
changes to pcm027.c and merge that.

-------------------------------------------------------------------
List admin: http://lists.arm.linux.org.uk/mailman/listinfo/linux-arm-kernel
FAQ:        http://www.arm.linux.org.uk/mailinglists/faq.php
Etiquette:  http://www.arm.linux.org.uk/mailinglists/etiquette.php

[Site Home]     [Linux Arm]     [Fedora ARM]     [Gcc Help]     [Git]     [DCCP]     [IETF Announce]     [Security]     [PDAs]     [Linux]     [Linux Book List]     [Linux MIPS]     [Yosemite Campsites]     [Photos]

Add to Google Google PageRank Checking tool