From: Michal Simek <monstr@monstr.eu>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] arch/microblaze changes for 3.12
Date: Mon, 09 Sep 2013 10:08:42 +0200 [thread overview]
Message-ID: <522D820A.9020304@monstr.eu> (raw)
In-Reply-To: <CA+55aFw6XSH2J4DALGF9Mp-sZHpFwiZnwoGYjiXH=rz5NkSeZA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1316 bytes --]
On 09/06/2013 08:09 PM, Linus Torvalds wrote:
> On Fri, Sep 6, 2013 at 2:09 AM, Michal Simek <monstr@monstr.eu> wrote:
>> Hi Linus,
>>
>> please pull these Microblaze patches to your tree.
>
> Hmm. You've started using signed tags, nice. I just wonder why you use
> use one that seems to be a relatively weak 1024-bit key (ID: 294A0C21)
> when you have stronger ones available?
>
> Not a huge deal, I'm just wondering.
I am using signed tags for Xilinx Zynq (arm-soc tree) for several months
because Olof asked for it. But this was the first time I used it for Microblaze.
The problem is that I can't see 2048-bit key in my secretkeys but it is
in my public key. Probably I removed it when I was playing with it.
I don't know if I can import this public subkey back to my secret key or
just revoke it. This is the reason why you can see stronger key but git can't use it.
BTW: In that time I setup my PC that I can even send signed patches with git send-email.
Thanks,
Michal
--
Michal Simek, Ing. (M.Eng), OpenPGP -> KeyID: FE3D1F91
w: www.monstr.eu p: +42-0-721842854
Maintainer of Linux kernel - Microblaze cpu - http://www.monstr.eu/fdt/
Maintainer of Linux kernel - Xilinx Zynq ARM architecture
Microblaze U-BOOT custodian and responsible for u-boot arm zynq platform
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 263 bytes --]
prev parent reply other threads:[~2013-09-09 8:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-06 9:09 [GIT PULL] arch/microblaze changes for 3.12 Michal Simek
2013-09-06 18:09 ` Linus Torvalds
2013-09-09 8:08 ` Michal Simek [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=522D820A.9020304@monstr.eu \
--to=monstr@monstr.eu \
--cc=linux-kernel@vger.kernel.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.