From: Mimi Zohar <zohar@linux.ibm.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
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, 06 Aug 2019 15:02:16 -0400 [thread overview]
Message-ID: <1565118136.11223.215.camel@linux.ibm.com> (raw)
In-Reply-To: <20190806134530.747d155e@canb.auug.org.au>
Hi Stephen,
On Tue, 2019-08-06 at 13:45 +1000, Stephen Rothwell wrote:
> 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.
ditto
>
> 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).
Based on the new "Documentation/maintainer/rebasing-and-merging.rst",
I'm under the impression that we shouldn't be rebasing, even for
"just" adding tags. Waiting for tags before pushing out to next-
integrity is causing delays, but we're trying out this approach. So
for now, I've included your commit.
thanks,
Mimi
next prev parent reply other threads:[~2019-08-06 19:02 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
2019-08-06 19:02 ` Mimi Zohar [this message]
-- 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=1565118136.11223.215.camel@linux.ibm.com \
--to=zohar@linux.ibm.com \
--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=sfr@canb.auug.org.au \
--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 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.