The pull request you sent on Sat, 18 May 2019 11:17:26 +0200:
> git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git efi-urgent-for-linus
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/39feaa3ff4453594297574e116a55bd6d5371f37
Thank you!
--
Deet-doot-dot, I am a
The pull request you sent on Sun, 03 Feb 2019 17:16:05 +0100:
> git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git efi-urgent-for-linus
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/89401be6580eab6419bab1f553144131e7a335dc
Thank you!
--
Deet-doot-dot, I am a
* Linus Torvalds wrote:
> On Thu, Jan 10, 2019 at 11:46 PM Ingo Molnar wrote:
> >
> > A single fix that adds an annotation to resolve a kmemleak false
> > positive.
>
> This one is apparently obviated by commit 80424b02d42b ("efi: Reduce
> the amount of memblock reservations for persistent al
* Linus Torvalds wrote:
> On Fri, Jan 11, 2019 at 6:22 AM Ard Biesheuvel
> wrote:
> >
> > I was hoping we could merge this patch (so we can backport it), but
> > resolve the conflict by dropping the kmemleak_ignore() again [..]
>
> Well, we'd drop the new #include line also, since it would be
On Fri, Jan 11, 2019 at 6:22 AM Ard Biesheuvel
wrote:
>
> I was hoping we could merge this patch (so we can backport it), but
> resolve the conflict by dropping the kmemleak_ignore() again [..]
Well, we'd drop the new #include line also, since it would be
pointless without the kmemleak_ignore().
On Thu, Jan 10, 2019 at 11:46 PM Ingo Molnar wrote:
>
> A single fix that adds an annotation to resolve a kmemleak false
> positive.
This one is apparently obviated by commit 80424b02d42b ("efi: Reduce
the amount of memblock reservations for persistent allocations")
Linus
On Fri, 11 Jan 2019 at 08:46, Ingo Molnar wrote:
>
> Linus,
>
> Please pull the latest efi-urgent-for-linus git tree from:
>
>git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
> efi-urgent-for-linus
>
># HEAD: b12f5440d8ca02e8f9ab4f1461f9214295cc4f66 Merge branch 'linus' into
> e
The pull request you sent on Fri, 30 Nov 2018 07:21:02 +0100:
> git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git efi-urgent-for-linus
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/8d9f412d51b84eafd2253a82120e218ddc53e721
Thank you!
--
Deet-doot-dot, I am a
On Sat, Sep 22, 2018 at 02:34:03PM +0200, Thomas Gleixner wrote:
> Greg,
>
> please pull the latest efi-urgent-for-linus git tree from:
>
>git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
> efi-urgent-for-linus
>
> Make the EFI arm stub device tree loader default on to unbreak exis
* Matt Fleming wrote:
> Folks, please pull the following fix for the v4.9 EFI queue sat in
> tip/efi/core.
>
> The following changes since commit 5465fe0fc3316f7cdda66732a7986f4ebe76d949:
>
> Merge tag 'efi-next' of
> git://git.kernel.org/pub/scm/linux/kernel/git/mfleming/efi into efi/core
* Josh Poimboeuf wrote:
> On Mon, May 23, 2016 at 01:08:01PM +0100, Matt Fleming wrote:
> > On Mon, 16 May, at 01:05:45PM, Linus Torvalds wrote:
> > >
> > > I think the right fix is to just get rid of that silly conditional
> > > frame pointer thing, and always use frame pointers in this stub
>
On Mon, May 23, 2016 at 01:08:01PM +0100, Matt Fleming wrote:
> On Mon, 16 May, at 01:05:45PM, Linus Torvalds wrote:
> >
> > I think the right fix is to just get rid of that silly conditional
> > frame pointer thing, and always use frame pointers in this stub
> > function. And then we don't need t
On Mon, 16 May, at 01:05:45PM, Linus Torvalds wrote:
>
> I think the right fix is to just get rid of that silly conditional
> frame pointer thing, and always use frame pointers in this stub
> function. And then we don't need that (odd) load to get the old stack
> pointer into %rax - we can just us
* Matt Fleming wrote:
> On Tue, 17 May, at 10:04:34AM, Matt Fleming wrote:
> >
> > Now I'm wondering whether other users of FRAME_BEGIN/FRAME_END make
> > this same mistake. Coccinelle might be able to detect it perhaps.
>
> A quick bit of sed turned up the code in arch/x86/entry/entry_64.S,
>
On Tue, 17 May, at 10:04:34AM, Matt Fleming wrote:
>
> Now I'm wondering whether other users of FRAME_BEGIN/FRAME_END make
> this same mistake. Coccinelle might be able to detect it perhaps.
A quick bit of sed turned up the code in arch/x86/entry/entry_64.S,
which looks to suffer from the same bu
On Mon, 16 May, at 01:05:45PM, Linus Torvalds wrote:
>
> So that whole 8-vs-16 offset confusion depends on the frame pointer!
> If frame pointers were enabled, it will be 16. If they weren't, it
> will be 8. That patch that changes it from 8 to 16 will just move the
> bug around. Before, it was co
On Mon, May 16, 2016 at 03:23:51PM -0500, Alex Thorlton wrote:
> Everything discussed above makes sense to me, and the patch looks sane.
> I will apply and test it today and let you know how it works.
I applied this to the latest -tip kernel and tested on both real
hardware and in our simulator.
On Mon, May 16, 2016 at 01:05:45PM -0700, Linus Torvalds wrote:
> On Mon, May 16, 2016 at 7:46 AM, Ingo Molnar wrote:
> >
> > Please pull the latest efi-urgent-for-linus git tree from:
> >
> >git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
> > efi-urgent-for-linus
> >
> ># HEAD:
On Mon, May 16, 2016 at 7:46 AM, Ingo Molnar wrote:
>
> Please pull the latest efi-urgent-for-linus git tree from:
>
>git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
> efi-urgent-for-linus
>
># HEAD: bea23c757f66d91dac8fdadd94da0cba6b0b66bc x86/efi: Fix 7th argument
> to efi_ca
19 matches
Mail list logo
