All of lore.kernel.org
 help / color / mirror / Atom feed
From: Simon Glass <sjg@chromium.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v3 2/8] efi: Use asmlinkage for EFIAPI
Date: Mon, 7 Nov 2016 07:45:55 -0800	[thread overview]
Message-ID: <CAPnjgZ10vqdLTTzd3KoBMVtLiDxiB_MgEewHGZ-fWGU3+W2FZQ@mail.gmail.com> (raw)
In-Reply-To: <7d24232c-356c-6142-f0dc-5ebc189a8b49@suse.de>

Hi Alex,

On 19 October 2016 at 01:11, Alexander Graf <agraf@suse.de> wrote:
>
>
> On 18/10/2016 22:37, Simon Glass wrote:
>> Hi Alex,
>>
>> On 18 October 2016 at 01:12, Alexander Graf <agraf@suse.de> wrote:
>>> On 10/18/2016 04:29 AM, Simon Glass wrote:
>>>>
>>>> This is required for x86 and is also correct for ARM (since it is empty).
>>>>
>>>> Signed-off-by: Simon Glass <sjg@chromium.org>
>>>> Reviewed-by: Bin Meng <bmeng.cn@gmail.com>
>>>
>>>
>>> (Replying here in lack for a cover letter)
>>>
>>> Could you please rebase your patches on top of
>>>
>>>   https://github.com/agraf/u-boot.git efi-next
>>>
>>> so that all the patches that I already queued are not repeated in the patch
>>> set and we don't get any conflicts?
>>
>> I can do that - but is this targeting -next? I was expecting these
>> patches to land in master.
>
> Sorry, they are on their way to master. It's just old habit wrt my
> naming scheme:
>
>   -next: current development branch, basically staging for master

I'd suggest calling that 'master'.

>   -release-number: future patches that I already applied proactively for
> the next release, or backports :)
>
> As it stands, I've only taken the base patches, not all of them. Would
> you expect all of the x86 efi enablement to land in 2016.11?

No, let's target the release after that.

Regards,
Simon

  reply	other threads:[~2016-11-07 15:45 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-18  2:29 [U-Boot] [PATCH v3 1/8] x86: Add implementations of setjmp() and longjmp() Simon Glass
2016-10-18  2:29 ` [U-Boot] [PATCH v3 2/8] efi: Use asmlinkage for EFIAPI Simon Glass
2016-10-18  7:12   ` Alexander Graf
2016-10-18 20:37     ` Simon Glass
2016-10-19  7:11       ` Alexander Graf
2016-11-07 15:45         ` Simon Glass [this message]
2016-10-18  2:29 ` [U-Boot] [PATCH v3 3/8] efi: Fix missing EFIAPI specifiers Simon Glass
2016-10-18  2:29 ` [U-Boot] [PATCH v3 4/8] x86: Tidy up selection of building the EFI stub Simon Glass
2016-10-18  3:07   ` Bin Meng
2016-10-18  2:29 ` [U-Boot] [PATCH v3 5/8] arm: efi: Add a hello world test program Simon Glass
2016-10-18  2:29 ` [U-Boot] [PATCH v3 6/8] x86: efi: Add EFI loader support for x86 Simon Glass
2016-10-18  2:29 ` [U-Boot] [PATCH v3 7/8] x86: efi: Add a hello world test program Simon Glass
2016-10-18  3:06   ` Bin Meng
2016-10-18  7:14   ` Alexander Graf
2016-10-18 20:37     ` Simon Glass
2016-10-19  7:09       ` Alexander Graf
2016-11-07 15:46         ` Simon Glass
2016-11-07 16:32           ` Alexander Graf
2016-11-11 16:17             ` Simon Glass
2016-11-12  6:23               ` Alexander Graf
2016-11-14 20:44                 ` Simon Glass
2016-11-14 20:46                   ` Alexander Graf
2016-11-14 20:58                     ` Simon Glass
2016-11-14 21:24                       ` Alexander Graf
2016-11-14 21:35                         ` Simon Glass
2016-10-18  2:29 ` [U-Boot] [PATCH v3 8/8] x86: Enable EFI loader support Simon Glass
2016-10-18  3:02 ` [U-Boot] [PATCH v3 1/8] x86: Add implementations of setjmp() and longjmp() Bin Meng
2016-10-18  3:20   ` Bin Meng

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=CAPnjgZ10vqdLTTzd3KoBMVtLiDxiB_MgEewHGZ-fWGU3+W2FZQ@mail.gmail.com \
    --to=sjg@chromium.org \
    --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 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.