From: Greg KH <gregkh@linuxfoundation.org>
To: Jonathan Cameron <jonathan.cameron@huawei.com>
Cc: Jonathan Cameron <jic23@kernel.org>, linux-iio@vger.kernel.org
Subject: Re: [PULL] First set of new device support, cleanups and features for IIO in the 5.4 cycle.
Date: Tue, 13 Aug 2019 15:56:56 +0200 [thread overview]
Message-ID: <20190813135656.GA27392@kroah.com> (raw)
In-Reply-To: <20190813143421.000070c0@huawei.com>
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
prev parent reply other threads:[~2019-08-13 13:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-12 20:04 [PULL] First set of new device support, cleanups and features for IIO in the 5.4 cycle Jonathan Cameron
2019-08-12 20:59 ` Greg KH
2019-08-13 8:14 ` Greg KH
2019-08-13 13:34 ` Jonathan Cameron
2019-08-13 13:56 ` Greg KH [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190813135656.GA27392@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=jic23@kernel.org \
--cc=jonathan.cameron@huawei.com \
--cc=linux-iio@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.