From: Greg KH <greg@kroah.com>
To: Mark Brown <broonie@kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Phillip Potter <phil@philpotter.co.uk>
Subject: Re: build failure after merge of the staging tree
Date: Fri, 30 Jul 2021 16:15:27 +0200 [thread overview]
Message-ID: <YQQJf7Lrj7p6RvU/@kroah.com> (raw)
In-Reply-To: <20210730140454.GZ4670@sirena.org.uk>
On Fri, Jul 30, 2021 at 03:04:54PM +0100, Mark Brown wrote:
> On Fri, Jul 30, 2021 at 04:02:41PM +0200, Greg KH wrote:
>
> > Ah, are you building with O= ? That might be the problem here, I think
> > I had to fix up that mess with the older driver in the past...
>
> Yes, all the -next integration builds use O= to keep the working trees
> between builds.
Yup, just tested this locally, that's the issue. Let me make a patch
series to fix this, thanks for the report...
greg k-h
next prev parent reply other threads:[~2021-07-30 14:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-30 13:53 build failure after merge of the staging tree Mark Brown
2021-07-30 14:02 ` Greg KH
2021-07-30 14:04 ` Mark Brown
2021-07-30 14:15 ` Greg KH [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-07-30 13:52 Mark Brown
2021-07-30 14:00 ` Greg KH
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=YQQJf7Lrj7p6RvU/@kroah.com \
--to=greg@kroah.com \
--cc=broonie@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=phil@philpotter.co.uk \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox