public inbox for linux-efi@vger.kernel.org
 help / color / mirror / Atom feed
From: Matt Fleming <matt-HNK1S37rvNbeXh+fF434Mdi2O/JbrIOy@public.gmane.org>
To: "Tangri,
	Saurabh" <saurabh.tangri-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: linux-efi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: Refactoring and cleanup patch on x86/efi
Date: Mon, 9 Jun 2014 14:41:27 +0100	[thread overview]
Message-ID: <20140609134127.GD27302@console-pimps.org> (raw)
In-Reply-To: <20140606132606.GA27302-HNK1S37rvNbeXh+fF434Mdi2O/JbrIOy@public.gmane.org>

On Fri, 06 Jun, at 02:26:06PM, Matt Fleming wrote:
> On Wed, 04 Jun, at 02:09:15PM, Tangri, Saurabh wrote:
> > x86/efi: Move all workarounds to a separate file quirks.c
> > 
> > Currently, it's difficult to find all the workarounds that are
> > applied when running on EFI, because they're littered throughout
> > various code paths. This change moves all of them into a separate
> > file with the hope that it will be come the single location for all
> > our well documented quirks.
> 
> Thanks Saurabh, applied to the 'next' branch. I had to rebase it against
> 'next' because there's been a few changes since the patches that are in
> the 'stable' branch.
> 
> Please double check to make sure that I did the rebase correctly,
> 
>   http://git.kernel.org/cgit/linux/kernel/git/mfleming/efi.git/commit/?h=next&id=fdf46c9f56a9fdcfc4e0b250e893cd7ffcecf0d5

Turns out I didn't apply it as carefully as I should have done, and the
kbuild bot noticed,

  https://lists.01.org/pipermail/kbuild-all/2014-June/004895.html

I've fixed this up and pushed it back out along with a commit that
should also fix the long standing sparse issue described in,

 https://lists.01.org/pipermail/kbuild-all/2014-June/004896.html

-- 
Matt Fleming, Intel Open Source Technology Center

      parent reply	other threads:[~2014-06-09 13:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-04 14:09 Refactoring and cleanup patch on x86/efi Tangri, Saurabh
     [not found] ` <D65204BE7F571446A6F75A899654E932723D6CFC-AtyAts71sc9Qxe9IK+vIArfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2014-06-06 13:26   ` Matt Fleming
     [not found]     ` <20140606132606.GA27302-HNK1S37rvNbeXh+fF434Mdi2O/JbrIOy@public.gmane.org>
2014-06-09 13:41       ` Matt Fleming [this message]

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=20140609134127.GD27302@console-pimps.org \
    --to=matt-hnk1s37rvnbexh+ff434mdi2o/jbrioy@public.gmane.org \
    --cc=linux-efi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=saurabh.tangri-ral2JQCrhuEAvxtiuMwx3w@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox