All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matt Fleming <matt-mF/unelCI9GS6iBeEJttW/XRex20P6io@public.gmane.org>
To: Geliang Tang <geliangtang-9Onoh4P/yGk@public.gmane.org>
Cc: linux-efi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH] efivars: use to_efivar_entry
Date: Fri, 8 Jan 2016 11:47:51 +0000	[thread overview]
Message-ID: <20160108114751.GF2532@codeblueprint.co.uk> (raw)
In-Reply-To: <044a291472c1df670c9b1247071f7af3a2c49a7d.1452003358.git.geliangtang-9Onoh4P/yGk@public.gmane.org>

On Tue, 05 Jan, at 10:17:17PM, Geliang Tang wrote:
> Use to_efivar_entry() instead of open-coding it.
> 
> Signed-off-by: Geliang Tang <geliangtang-9Onoh4P/yGk@public.gmane.org>
> ---
>  drivers/firmware/efi/efivars.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)

Thanks, applied for v4.6.

WARNING: multiple messages have this Message-ID (diff)
From: Matt Fleming <matt@codeblueprint.co.uk>
To: Geliang Tang <geliangtang@163.com>
Cc: linux-efi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] efivars: use to_efivar_entry
Date: Fri, 8 Jan 2016 11:47:51 +0000	[thread overview]
Message-ID: <20160108114751.GF2532@codeblueprint.co.uk> (raw)
In-Reply-To: <044a291472c1df670c9b1247071f7af3a2c49a7d.1452003358.git.geliangtang@163.com>

On Tue, 05 Jan, at 10:17:17PM, Geliang Tang wrote:
> Use to_efivar_entry() instead of open-coding it.
> 
> Signed-off-by: Geliang Tang <geliangtang@163.com>
> ---
>  drivers/firmware/efi/efivars.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)

Thanks, applied for v4.6.

  parent reply	other threads:[~2016-01-08 11:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-05 14:17 [PATCH] efivars: use to_efivar_entry Geliang Tang
2016-01-05 14:17 ` Geliang Tang
     [not found] ` <044a291472c1df670c9b1247071f7af3a2c49a7d.1452003358.git.geliangtang-9Onoh4P/yGk@public.gmane.org>
2016-01-08 11:47   ` Matt Fleming [this message]
2016-01-08 11:47     ` Matt Fleming

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=20160108114751.GF2532@codeblueprint.co.uk \
    --to=matt-mf/unelci9gs6ibeejttw/xrex20p6io@public.gmane.org \
    --cc=geliangtang-9Onoh4P/yGk@public.gmane.org \
    --cc=linux-efi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.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.