public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Chris Clayton <chris2553@googlemail.com>
Cc: Thomas Backlund <tmb@tmb.nu>, LKML <linux-kernel@vger.kernel.org>,
	stable@vger.kernel.org, torvic9@mailbox.org,
	Josh Poimboeuf <jpoimboe@redhat.com>
Subject: Re: linux-5.10.11 build failure
Date: Mon, 1 Feb 2021 10:37:54 +0100	[thread overview]
Message-ID: <YBfL8s138/HvX5Sb@kroah.com> (raw)
In-Reply-To: <064cf941-e7cb-e939-2bd1-f0dc2850cda7@googlemail.com>

On Mon, Feb 01, 2021 at 08:59:09AM +0000, Chris Clayton wrote:
> Hi Greg,
> 
> On 29/01/2021 15:14, Josh Poimboeuf wrote:
> > On Fri, Jan 29, 2021 at 12:09:53PM +0100, Greg Kroah-Hartman wrote:
> >> On Fri, Jan 29, 2021 at 11:03:26AM +0000, Chris Clayton wrote:
> >>>
> >>>
> >>> On 29/01/2021 10:11, Greg Kroah-Hartman wrote:
> >>>> On Thu, Jan 28, 2021 at 10:00:15AM -0600, Josh Poimboeuf wrote:
> ...
> >>>>
> >>>> It is in Linus's tree now :)
> >>>>
> >>>> Now grabbed.
> >>>>
> >>>
> >>> Are you sure, Greg? I don't see the patch in Linus' tree at
> >>> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git. Nor do is see it in your stable queue at
> >>> https://git.kernel.org/pub/scm/linux/kernel/git/stable/stable-queue.git/. For clarity, I've attached the patch which
> >>> fixes problem I reported and is currently sat in https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git As I
> >>> understand it, the patch is scheduled to be included in a pull request to Linus this weekend in time for -rc6.
> >>>
> >>> In fact, I did a pull from Linus' tree a few minutes ago and the build failed in the way I reported in this thread. I
> >>> added the patch and the build now succeeds.
> >>
> >> Ok, sorry, no, I grabbed 1d489151e9f9 ("objtool: Don't fail on missing
> >> symbol table") which is what Josh asked me to take.  I got that confused
> >> here.
> > 
> > I'm probably responsible for that confusion, I got mixed up myself.
> > It'll be a good idea to take both anyway.
> > 
> 
> The patch is now in Linus' tree at 5e6dca82bcaa49348f9e5fcb48df4881f6d6c4ae

Thanks, now queued up.

greg k-h

  reply	other threads:[~2021-02-01  9:38 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-28 11:24 linux-5.10.11 build failure Thomas Backlund
2021-01-28 13:38 ` Chris Clayton
2021-01-28 14:41   ` Greg Kroah-Hartman
2021-01-28 15:36     ` Chris Clayton
2021-01-28 16:00   ` Josh Poimboeuf
     [not found]     ` <YBPfQXSrz+P3TOZf@kroah.com>
     [not found]       ` <f9f8e2c9-3690-52f3-8d96-4f2b735dd6bd@googlemail.com>
     [not found]         ` <YBPtAYK1Nj/WpiTo@kroah.com>
     [not found]           ` <20210129151423.rsyubljbrzxicleq@treble>
2021-02-01  8:59             ` Chris Clayton
2021-02-01  9:37               ` Greg Kroah-Hartman [this message]
2021-01-28 15:52 ` Josh Poimboeuf
2021-01-28 16:03   ` Chris Clayton
  -- strict thread matches above, loose matches on Subject: below --
2021-01-28 10:19 torvic9
2021-01-28  9:17 Chris Clayton
2021-01-28  9:34 ` Greg Kroah-Hartman
2021-01-28 10:00   ` Bhaskar Chowdhury
2021-01-28 10:05   ` Chris Clayton

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=YBfL8s138/HvX5Sb@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=chris2553@googlemail.com \
    --cc=jpoimboe@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=tmb@tmb.nu \
    --cc=torvic9@mailbox.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox