All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Henderson <richard.henderson@linaro.org>
To: Jason Thorpe <thorpej@me.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [PATCH] qemu-palcode: Changes to support booting NetBSD/alpha
Date: Wed, 14 Oct 2020 20:32:02 -0700	[thread overview]
Message-ID: <709cbaaf-afe8-820c-9dd5-217bce626101@linaro.org> (raw)
In-Reply-To: <6896C79F-8A9B-4EFC-BC68-EE8856EFD2B6@me.com>

On 10/14/20 4:16 PM, Jason Thorpe wrote:
> 
>> On Oct 14, 2020, at 2:52 PM, Richard Henderson <richard.henderson@linaro.org> wrote:
>>
>> I'm certainly open to these changes.  But it'll need to be split up -- one
>> patch per bullet, basically.
> 
> That's fine.  What's the convention for patches that stack on top of one another?

git format-patch --cover-letter
git send-email --thread --no-chain-reply-to


r~


  reply	other threads:[~2020-10-15  3:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-07  2:52 [PATCH] qemu-palcode: Changes to support booting NetBSD/alpha Jason Thorpe
2020-10-14 21:52 ` Richard Henderson
2020-10-14 23:16   ` Jason Thorpe
2020-10-15  3:32     ` Richard Henderson [this message]
2020-10-15 10:58       ` Philippe Mathieu-Daudé

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=709cbaaf-afe8-820c-9dd5-217bce626101@linaro.org \
    --to=richard.henderson@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=thorpej@me.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 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.