On Fri, Feb 10, 2017 at 11:35:35PM +0100, Peter Rosin wrote: > > On Sun, Feb 05, 2017 at 10:35:02AM +0000, Jonathan Cameron wrote: > >> The following changes since commit 5c113b5e0082e90d2e1c7b12e96a7b8cf0623e27: > >> > >> iio: dht11: Use usleep_range instead of msleep for start signal (2017-01-22 13:35:40 +0000) > >> > >> are available in the git repository at: > >> > >> git://git.kernel.org/pub/scm/linux/kernel/git/jic23/iio.git tags/iio-fixes-for-4.10c > > > > It's a bit late for 4.10 for me, can I just pull this into my -next > > branch and will they get to 4.10.1 properly? Meaning, do that have cc: > > stable markings on them? Or do you want to fix that up and resend this > > request? > > Hi Greg, > > You should ask Ken Lin who has the HW and who is apparently affected. > I think it's bad that you are willing to have a known regression hit > v4.10 when all was fine in v4.9. Or perhaps you didn't realize that > the regression was from this cycle? > > The fixes are obvious. I don't understand your hesitation. My "hesitation" is that I'm about to get on a plane for a day or so and don't have the time to get this to Linus before 4.10-final is out this Sunday. Getting it in a week later should be ok, we all make mistakes, as long as we fix them it's all good, and for 4.10.1 should be ok. thanks, greg k-h -- To unsubscribe from this list: send the line "unsubscribe linux-iio" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
