linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jiri Kosina <jikos@kernel.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Benjamin Tissoires <benjamin.tissoires@redhat.com>,
	Linux Next Mailing List <linux-next@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Cristian Klein <cristian.klein@elastisys.com>,
	Nathan Chancellor <natechancellor@gmail.com>
Subject: Re: linux-next: build failures after merge of the hid tree
Date: Wed, 24 Jun 2020 00:13:57 +0200 (CEST)	[thread overview]
Message-ID: <nycvar.YFH.7.76.2006240012170.13242@cbobk.fhfr.pm> (raw)
In-Reply-To: <20200623103736.25f67de5@canb.auug.org.au>

On Tue, 23 Jun 2020, Stephen Rothwell wrote:

> > I don't know what caused it, but commit
> > 
> >   470376737e88 ("HID: allow building hid.ko as an external module")
> > 
> > did not fix it.  BTW, I build with "make O=...".

That's actually the patch that almost certainly broke it.

CCing Cristian (author of that patch) and Nathan, who apparently sent a 
fixup patch for this, but I haven't seen it, as our corporate mailserver 
had severe issues yesterday.

If there is no resolution by tomorrow, we'll just drop it.

-- 
Jiri Kosina
SUSE Labs


  parent reply	other threads:[~2020-06-23 22:14 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-21  4:04 linux-next: build failures after merge of the hid tree Stephen Rothwell
2020-06-23  0:37 ` Stephen Rothwell
2020-06-23 14:24   ` Benjamin Tissoires
2020-06-23 22:13   ` Jiri Kosina [this message]
2020-06-24  2:27     ` Nathan Chancellor
2020-06-24  7:30     ` Jiri Kosina
2020-06-24  8:01       ` Cristian Klein

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=nycvar.YFH.7.76.2006240012170.13242@cbobk.fhfr.pm \
    --to=jikos@kernel.org \
    --cc=benjamin.tissoires@redhat.com \
    --cc=cristian.klein@elastisys.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=natechancellor@gmail.com \
    --cc=sfr@canb.auug.org.au \
    /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).