Message ID | 20190812210428.1668b6d8@archlinux (mailing list archive) |
---|---|
State | New, archived |
Headers | show |
Series | [PULL] First set of new device support, cleanups and features for IIO in the 5.4 cycle. | expand |
On Mon, Aug 12, 2019 at 09:04:28PM +0100, Jonathan Cameron wrote: > The following changes since commit e59fc52529118aaad9aa666f25530dde6e2180e9: > > staging: rtl8192*: display ESSIDs using %pE (2019-07-25 14:38:52 +0200) > > are available in the Git repository at: > > git://git.kernel.org/pub/scm/linux/kernel/git/jic23/iio.git tags/iio-for-5.4a Pulled and pushed out, thanks. greg k-h
On Mon, Aug 12, 2019 at 10:59:32PM +0200, Greg KH wrote: > On Mon, Aug 12, 2019 at 09:04:28PM +0100, Jonathan Cameron wrote: > > The following changes since commit e59fc52529118aaad9aa666f25530dde6e2180e9: > > > > staging: rtl8192*: display ESSIDs using %pE (2019-07-25 14:38:52 +0200) > > > > are available in the Git repository at: > > > > git://git.kernel.org/pub/scm/linux/kernel/git/jic23/iio.git tags/iio-for-5.4a > > Pulled and pushed out, thanks. 0-day gives me the following warning, did you not see this on your tree? Can you send me a patch to fix this up? thanks, greg k-h ---------------- tree/branch: https://kernel.googlesource.com/pub/scm/linux/kernel/git/gregkh/staging.git staging-testing branch HEAD: 6aed51d8912460cab375f7fc4ea834851e107b7a Merge tag 'iio-for-5.4a' of git://git.kernel.org/pub/scm/linux/kernel/git/jic23/iio into staging-next Regressions in current branch: drivers/iio/light/noa1305.c:87:9: warning: this statement may fall through [-Wimplicit-fallthrough=]
On Tue, 13 Aug 2019 10:14:19 +0200 Greg KH <gregkh@linuxfoundation.org> wrote: > On Mon, Aug 12, 2019 at 10:59:32PM +0200, Greg KH wrote: > > On Mon, Aug 12, 2019 at 09:04:28PM +0100, Jonathan Cameron wrote: > > > The following changes since commit e59fc52529118aaad9aa666f25530dde6e2180e9: > > > > > > staging: rtl8192*: display ESSIDs using %pE (2019-07-25 14:38:52 +0200) > > > > > > are available in the Git repository at: > > > > > > git://git.kernel.org/pub/scm/linux/kernel/git/jic23/iio.git tags/iio-for-5.4a > > > > Pulled and pushed out, thanks. > > 0-day gives me the following warning, did you not see this on your tree? Looks like my tree was based before the change that enabled the warning by default (I didn't check but a quick build shows it doesn't occur with iio.git/togreg and does with staging/staging-testing I can't actually find any completion message from 0-day so not sure if this hit an outage or if I'm not getting the completion messages for some reason. Oops on missing this one in review! > > Can you send me a patch to fix this up? On it's way. Jonathan > > thanks, > > greg k-h > > ---------------- > tree/branch: https://kernel.googlesource.com/pub/scm/linux/kernel/git/gregkh/staging.git staging-testing > branch HEAD: 6aed51d8912460cab375f7fc4ea834851e107b7a Merge tag 'iio-for-5.4a' of git://git.kernel.org/pub/scm/linux/kernel/git/jic23/iio into staging-next > > Regressions in current branch: > > drivers/iio/light/noa1305.c:87:9: warning: this statement may fall through [-Wimplicit-fallthrough=] > >
On Tue, Aug 13, 2019 at 02:34:21PM +0100, Jonathan Cameron wrote: > On Tue, 13 Aug 2019 10:14:19 +0200 > Greg KH <gregkh@linuxfoundation.org> wrote: > > > On Mon, Aug 12, 2019 at 10:59:32PM +0200, Greg KH wrote: > > > On Mon, Aug 12, 2019 at 09:04:28PM +0100, Jonathan Cameron wrote: > > > > The following changes since commit e59fc52529118aaad9aa666f25530dde6e2180e9: > > > > > > > > staging: rtl8192*: display ESSIDs using %pE (2019-07-25 14:38:52 +0200) > > > > > > > > are available in the Git repository at: > > > > > > > > git://git.kernel.org/pub/scm/linux/kernel/git/jic23/iio.git tags/iio-for-5.4a > > > > > > Pulled and pushed out, thanks. > > > > 0-day gives me the following warning, did you not see this on your tree? > > Looks like my tree was based before the change that enabled the warning > by default (I didn't check but a quick build shows it doesn't occur with > iio.git/togreg and does with staging/staging-testing That compiler isn't "on" yet in our trees, which is why we all missed it locally. > I can't actually find any completion message from 0-day so not sure if this > hit an outage or if I'm not getting the completion messages for some reason. 0-day is being slow/flakey these days :( > Oops on missing this one in review! Not a problem, nice to see it's an actual bug :) thanks, greg k-h