Kernel keyring development
 help / color / mirror / Atom feed
From: Jarkko Sakkinen <jarkko@kernel.org>
To: Gabriel Krisman Bertazi <krisman@collabora.com>
Cc: dhowells@redhat.com, keyrings@vger.kernel.org, kernel@collabora.com
Subject: Re: [PATCH v2] watch_queue: Drop references to /dev/watch_queue
Date: Sun, 29 Nov 2020 04:38:36 +0200	[thread overview]
Message-ID: <20201129023836.GA39488@kernel.org> (raw)
In-Reply-To: <20201124202802.645739-1-krisman@collabora.com>

On Tue, Nov 24, 2020 at 03:28:02PM -0500, Gabriel Krisman Bertazi wrote:
> The merged API doesn't use a watch_queue device, but instead relies on
> pipes, so let the documentation reflect that.
> 
> Fixes: f7e47677e39a ("watch_queue: Add a key/keyring notification facility")
> Cc: David Howells <dhowells@redhat.com>
> Signed-off-by: Gabriel Krisman Bertazi <krisman@collabora.com>

Acked-by: Jarkko Sakkinen <jarkko@kernel.org>

/Jarkko

      reply	other threads:[~2020-11-29  2:39 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-24 20:28 [PATCH v2] watch_queue: Drop references to /dev/watch_queue Gabriel Krisman Bertazi
2020-11-29  2:38 ` Jarkko Sakkinen [this message]

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=20201129023836.GA39488@kernel.org \
    --to=jarkko@kernel.org \
    --cc=dhowells@redhat.com \
    --cc=kernel@collabora.com \
    --cc=keyrings@vger.kernel.org \
    --cc=krisman@collabora.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