mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Kirill Smelkov <kirr@nexedi.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Al Viro <viro@zeniv.linux.org.uk>, Arnd Bergmann <arnd@arndb.de>,
	Christoph Hellwig <hch@lst.de>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Pavel Machek <pavel@denx.de>,
	Rasmus Villemoes <linux@rasmusvillemoes.dk>,
	Miklos Szeredi <miklos@szeredi.hu>,
	linux-fsdevel <linux-fsdevel@vger.kernel.org>,
	Linux List Kernel Mailing <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/3] stream_open bits for Linux 5.2
Date: Wed, 08 May 2019 07:40:58 +0000	[thread overview]
Message-ID: <20190508074048.GA2907@deco.navytux.spb.ru> (raw)
In-Reply-To: <CAHk-=wgWusqMfU25eBofgBHVSrQaVxr-EwCPCWcBaFMjzf_=Cg@mail.gmail.com>

On Tue, May 07, 2019 at 12:18:03PM -0700, Linus Torvalds wrote:
> On Tue, May 7, 2019 at 12:09 PM Kirill Smelkov <kirr@nexedi.com> wrote:
> >
> > I've pushed corresponding gpg-signed tag (stream_open-5.2) to my tree. I
> > did not go the gpg way initially because we do not have a gpg-trust
> > relation established and so I thought that signing was useless.
> 
> Ok, since I hadn't pushed out my pull yet, I just re-did it with your
> signature, so that the key is visible in the git tree.

Thanks.

      reply	other threads:[~2019-05-08  8:11 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-06 17:20 Kirill Smelkov
2019-05-06 17:20 ` [PATCH 1/3] dtlk: remove double call to nonseekable_open Kirill Smelkov
2019-05-06 17:34 ` [PATCH 3/3] vfs: pass ppos=NULL to .read()/.write() of FMODE_STREAM files Kirill Smelkov
2019-05-07 18:54 ` [PATCH 0/3] stream_open bits for Linux 5.2 Linus Torvalds
2019-05-07 19:09   ` Kirill Smelkov
2019-05-07 19:18     ` Linus Torvalds
2019-05-08  7:40       ` Kirill Smelkov [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=20190508074048.GA2907@deco.navytux.spb.ru \
    --to=kirr@nexedi.com \
    --cc=arnd@arndb.de \
    --cc=gregkh@linuxfoundation.org \
    --cc=hch@lst.de \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@rasmusvillemoes.dk \
    --cc=miklos@szeredi.hu \
    --cc=pavel@denx.de \
    --cc=torvalds@linux-foundation.org \
    --cc=viro@zeniv.linux.org.uk \
    /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
all inboxes | Powered by JetHome®