From: Roman Kopytin <Roman.Kopytin@kaspersky.com>
To: Rasmus Villemoes <rasmus.villemoes@prevas.dk>,
U-Boot-Denx <u-boot@lists.denx.de>
Subject: RE: [PATCH] tools: add fdt_add_pubkey
Date: Thu, 5 Aug 2021 07:59:03 +0000 [thread overview]
Message-ID: <01117eb580f24ffe9277fbb5505bdf6c@kaspersky.com> (raw)
In-Reply-To: <38004e18-5176-a3f5-6442-7a5016d48247@prevas.dk>
Thanks a lot.
Can I create 1 patch with tool + test?
-----Original Message-----
From: Rasmus Villemoes <rasmus.villemoes@prevas.dk>
Sent: Thursday, August 5, 2021 10:56 AM
To: Roman Kopytin <Roman.Kopytin@kaspersky.com>; U-Boot-Denx <u-boot@lists.denx.de>
Subject: Re: [PATCH] tools: add fdt_add_pubkey
Caution: This is an external email. Be cautious while opening links or attachments.
On 03/08/2021 13.00, Roman Kopytin wrote:
Hi Roman
Thanks for picking this up. A few notes on the process:
- Don't attach the patch, it must be inline in the email. But do not copy-paste it in to your mail client, that will most likely make it whitespace-damaged. git send-email is your friend.
- Sending it to u-boot@lists.denx.de is correct, but you should also cc "interested parties", e.g. at least me (for obvious reasons) and anybody who participated in the earlier thread. If you had used git send-email, your "Cc: " line in the patch would actually automatically have included me on cc. Other people are just as easy to add (with the --cc option to "git send-email"). Very few people, if any, read every message on the U-Boot mailing list.
- It would be good if you could also add a test and ensure that it works. I think my original submission had three commits, of which the first is now moot, but that last patch was a test case. It may need some adjustments to apply nowadays, but it should give you a starting point.
Rasmus
next prev parent reply other threads:[~2021-08-05 7:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-03 11:00 [PATCH] tools: add fdt_add_pubkey Roman Kopytin
2021-08-05 7:55 ` Rasmus Villemoes
2021-08-05 7:59 ` Roman Kopytin [this message]
2021-08-06 10:03 ` Rasmus Villemoes
2021-08-06 11:28 ` Steffen Jaeckel
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=01117eb580f24ffe9277fbb5505bdf6c@kaspersky.com \
--to=roman.kopytin@kaspersky.com \
--cc=rasmus.villemoes@prevas.dk \
--cc=u-boot@lists.denx.de \
/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