From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Thiago Jung Bauermann <bauerman@linux.ibm.com>
Cc: Mimi Zohar <zohar@linux.vnet.ibm.com>,
Dmitry Kasatkin <dmitry.kasatkin@gmail.com>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
Philipp Rudo <prudo@linux.ibm.com>, Jessica Yu <jeyu@kernel.org>
Subject: Re: linux-next: build failure after merge of the integrity tree
Date: Tue, 6 Aug 2019 13:45:30 +1000 [thread overview]
Message-ID: <20190806134530.747d155e@canb.auug.org.au> (raw)
In-Reply-To: <87imrb0yoh.fsf@morokweng.localdomain>
[-- Attachment #1: Type: text/plain, Size: 547 bytes --]
Hi Thiago,
On Tue, 06 Aug 2019 00:18:06 -0300 Thiago Jung Bauermann <bauerman@linux.ibm.com> wrote:
>
> Sorry for the trouble. I wasn't aware of that build time check.
> I'll enable HEADER_TEST and KERNEL_HEADER_TEST for my next patches.
I do allmodconfig builds which enable those.
> Thanks for providing the fix. Should I post a new version or can Mimi
> squash the above into the original patch?
Up to Mimi, but either works (or just committing my patch if the tree is
normally not rebased).
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2019-08-06 3:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-06 2:15 linux-next: build failure after merge of the integrity tree Stephen Rothwell
2019-08-06 3:18 ` Thiago Jung Bauermann
2019-08-06 3:45 ` Stephen Rothwell [this message]
2019-08-06 19:02 ` Mimi Zohar
-- strict thread matches above, loose matches on Subject: below --
2023-02-07 0:51 Stephen Rothwell
2023-02-07 12:48 ` Roberto Sassu
2019-06-14 5:34 Stephen Rothwell
2019-06-14 14:09 ` Mimi Zohar
2018-07-17 4:40 Stephen Rothwell
2018-07-17 13:18 ` Mimi Zohar
2018-07-17 22:21 ` Stephen Rothwell
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=20190806134530.747d155e@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=bauerman@linux.ibm.com \
--cc=dmitry.kasatkin@gmail.com \
--cc=jeyu@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=prudo@linux.ibm.com \
--cc=zohar@linux.vnet.ibm.com \
/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;
as well as URLs for NNTP newsgroup(s).