public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: Ard Biesheuvel <ard.biesheuvel@linaro.org>
To: Ryan Harkin <ryan.harkin@linaro.org>
Cc: "edk2-devel@lists.01.org" <edk2-devel@lists.01.org>,
	Leif Lindholm <leif.lindholm@linaro.org>
Subject: Re: [PATCH v4 0/4] Juno cleanup -- OpenPlatformPkg edition
Date: Wed, 5 Apr 2017 15:11:55 +0100	[thread overview]
Message-ID: <CAKv+Gu8tEKuxBFtiDtse0Jm-c_bCxPELS4yfZi13DA3cJR3N_Q@mail.gmail.com> (raw)
In-Reply-To: <CAD0U-hKKV7Zm4PXFX3c2x+cy-vsbtmkg04BHXB9uk=PM3YsZHw@mail.gmail.com>

On 5 April 2017 at 15:10, Ryan Harkin <ryan.harkin@linaro.org> wrote:
> On 5 April 2017 at 15:00, Ard Biesheuvel <ard.biesheuvel@linaro.org> wrote:
>> Counterpart to the EDK2 series switching Juno to the generic non-discoverable
>> device driver and generic PCI host bridge driver.
>>
>> v4: fixed a number of non-functional issues -- include ordering, incorrect
>>     BASE_NAME, commit log clarifications
>>     add RBs and TBs
>
> I don't see my TBs in there, is gmail messing me about or are they not there?
>

That appears to be caused by poor git send-email skills on my part,
unfortunately. I added the locally, though, so I will include them
when merging.

Thanks,
Ard.


  reply	other threads:[~2017-04-05 14:11 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-05 14:00 [PATCH v4 0/4] Juno cleanup -- OpenPlatformPkg edition Ard Biesheuvel
2017-04-05 14:00 ` [PATCH v4 1/4] Platforms/Juno: add non-discoverable device driver and library Ard Biesheuvel
2017-04-05 14:00 ` [PATCH v4 2/4] Platforms/Juno: add PciHostBridgeLib implementation Ard Biesheuvel
2017-04-05 15:02   ` Leif Lindholm
2017-04-05 14:00 ` [PATCH v4 3/4] Platforms/Juno: switch to generic PCI host bridge driver Ard Biesheuvel
2017-04-05 14:00 ` [PATCH v4 4/4] Platforms/Juno: remove BdsLib dependency Ard Biesheuvel
2017-04-05 14:10 ` [PATCH v4 0/4] Juno cleanup -- OpenPlatformPkg edition Ryan Harkin
2017-04-05 14:11   ` Ard Biesheuvel [this message]
2017-04-05 15:08     ` Ard Biesheuvel

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-list 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=CAKv+Gu8tEKuxBFtiDtse0Jm-c_bCxPELS4yfZi13DA3cJR3N_Q@mail.gmail.com \
    --to=devel@edk2.groups.io \
    /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