From: Arnd Bergmann <arnd@arndb.de>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org,
DRI mailing list <dri-devel@lists.freedesktop.org>,
linaro-mm-sig@lists.linaro.org, akpm@linux-foundation.org,
Sumit Semwal <sumit.semwal@linaro.org>,
linux-media@vger.kernel.org
Subject: Re: [GIT PULL]: dma-buf updates for 3.5
Date: Sat, 26 May 2012 07:48:29 +0000 [thread overview]
Message-ID: <201205260748.29800.arnd@arndb.de> (raw)
In-Reply-To: <CA+55aFy9QysTkgPuy=GPxknRMoPTSTmp3FkHFJ+bs0G6CSh41g@mail.gmail.com>
On Friday 25 May 2012, Linus Torvalds wrote:
> Please do something like
>
> gpg --keyserver pgp.mit.edu --send-keys 7126925D
>
> to actually make your public key public.
>
> Of course, if it isn't public, I assume it hasn't actually been signed
> by anybody, which makes it largely useless. But any future signing
> action will validate the pre-signing uses of the key, so that's
> fixable.
We have a Linaro meeting this week, so we will make sure to get this
key and other relevant ones signed by everyone who is here and in the
kernel keyring.
Arnd
WARNING: multiple messages have this Message-ID (diff)
From: Arnd Bergmann <arnd@arndb.de>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Sumit Semwal <sumit.semwal@linaro.org>,
linux-kernel@vger.kernel.org,
DRI mailing list <dri-devel@lists.freedesktop.org>,
linaro-mm-sig@lists.linaro.org, linux-media@vger.kernel.org,
Jesse Barker <jesse.barker@linaro.org>,
akpm@linux-foundation.org, Daniel Vetter <daniel@ffwll.ch>,
Dave Airlie <airlied@linux.ie>
Subject: Re: [GIT PULL]: dma-buf updates for 3.5
Date: Sat, 26 May 2012 07:48:29 +0000 [thread overview]
Message-ID: <201205260748.29800.arnd@arndb.de> (raw)
In-Reply-To: <CA+55aFy9QysTkgPuy=GPxknRMoPTSTmp3FkHFJ+bs0G6CSh41g@mail.gmail.com>
On Friday 25 May 2012, Linus Torvalds wrote:
> Please do something like
>
> gpg --keyserver pgp.mit.edu --send-keys 7126925D
>
> to actually make your public key public.
>
> Of course, if it isn't public, I assume it hasn't actually been signed
> by anybody, which makes it largely useless. But any future signing
> action will validate the pre-signing uses of the key, so that's
> fixable.
We have a Linaro meeting this week, so we will make sure to get this
key and other relevant ones signed by everyone who is here and in the
kernel keyring.
Arnd
next prev parent reply other threads:[~2012-05-26 7:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-25 7:55 [GIT PULL]: dma-buf updates for 3.5 Sumit Semwal
2012-05-25 9:17 ` Sumit Semwal
2012-05-25 16:44 ` Linus Torvalds
2012-05-26 7:48 ` Arnd Bergmann [this message]
2012-05-26 7:48 ` Arnd Bergmann
2012-05-26 14:17 ` Sumit Semwal
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=201205260748.29800.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=akpm@linux-foundation.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=linaro-mm-sig@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=sumit.semwal@linaro.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.