public inbox for linux-next@vger.kernel.org
 help / color / mirror / Atom feed
From: David Howells <dhowells@redhat.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: dhowells@redhat.com,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	James Morris <james.morris@microsoft.com>
Subject: Re: linux-next: Fixes tag needs some work in Linus' tree
Date: Wed, 20 Feb 2019 21:36:56 +0000	[thread overview]
Message-ID: <28431.1550698616@warthog.procyon.org.uk> (raw)
In-Reply-To: <20190221073835.7a18f007@canb.auug.org.au>

Stephen Rothwell <sfr@canb.auug.org.au> wrote:

> In commit
> 
>   822ad64d7e46 ("keys: Fix dependency loop between construction record and auth key")
> 
> Fixes tag
> 
>   Fixes: 7ee02a316600 ("keys: Fix dependency loop between construction record and auth key")
> 
> has these problem(s):
> 
>   - Target SHA1 does not exist

Oops.  I guess I pasted in the wrong commit details.

	commit 76181c134f87479fa13bf2548ddf2999055d34d4
	KEYS: Make request_key() and co fundamentally asynchronous

should've been it.

David

  reply	other threads:[~2019-02-20 21:36 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-20 20:38 linux-next: Fixes tag needs some work in Linus' tree Stephen Rothwell
2019-02-20 21:36 ` David Howells [this message]
  -- strict thread matches above, loose matches on Subject: below --
2021-09-21  2:10 Stephen Rothwell
2019-02-21 20:16 Stephen Rothwell
2019-02-18 20:33 Stephen Rothwell
2019-02-19  1:58 ` Changbin Du
2019-02-02 21:28 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=28431.1550698616@warthog.procyon.org.uk \
    --to=dhowells@redhat.com \
    --cc=james.morris@microsoft.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    --cc=torvalds@linux-foundation.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