All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matt Fleming <matt-mF/unelCI9GS6iBeEJttW/XRex20P6io@public.gmane.org>
To: Will Deacon <will.deacon-5wv7dgnIgG8@public.gmane.org>
Cc: Mark Rutland <mark.rutland-5wv7dgnIgG8@public.gmane.org>,
	linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
	Ard Biesheuvel
	<ard.biesheuvel-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>,
	Catalin Marinas <catalin.marinas-5wv7dgnIgG8@public.gmane.org>,
	Jeremy Linton <jeremy.linton-5wv7dgnIgG8@public.gmane.org>,
	Leif Lindholm
	<leif.lindholm-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>,
	linux-efi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH] arm64/efi: remove spurious WARN_ON for !4K kernels
Date: Fri, 17 Jun 2016 22:16:01 +0100	[thread overview]
Message-ID: <20160617211601.GN2658@codeblueprint.co.uk> (raw)
In-Reply-To: <20160603100040.GJ9915-5wv7dgnIgG8@public.gmane.org>

On Fri, 03 Jun, at 11:00:40AM, Will Deacon wrote:
> 
> Mark, Jeremy?
> 
> I've kept this patch marked as unread, but it's not clear to me (a) how
> urgent it is (b) what tree it should go through and (c) whether it's the
> right thing to do!

Ping? Anyone got an update here?

WARNING: multiple messages have this Message-ID (diff)
From: matt@codeblueprint.co.uk (Matt Fleming)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm64/efi: remove spurious WARN_ON for !4K kernels
Date: Fri, 17 Jun 2016 22:16:01 +0100	[thread overview]
Message-ID: <20160617211601.GN2658@codeblueprint.co.uk> (raw)
In-Reply-To: <20160603100040.GJ9915@arm.com>

On Fri, 03 Jun, at 11:00:40AM, Will Deacon wrote:
> 
> Mark, Jeremy?
> 
> I've kept this patch marked as unread, but it's not clear to me (a) how
> urgent it is (b) what tree it should go through and (c) whether it's the
> right thing to do!

Ping? Anyone got an update here?

  parent reply	other threads:[~2016-06-17 21:16 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-25 15:11 [PATCH] arm64/efi: remove spurious WARN_ON for !4K kernels Mark Rutland
2016-05-25 15:11 ` Mark Rutland
     [not found] ` <1464189116-30898-1-git-send-email-mark.rutland-5wv7dgnIgG8@public.gmane.org>
2016-05-25 15:23   ` Ard Biesheuvel
2016-05-25 15:23     ` Ard Biesheuvel
     [not found]     ` <BA565A9C-8CC0-42E4-9821-7941852F835A-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2016-05-25 16:12       ` Mark Rutland
2016-05-25 16:12         ` Mark Rutland
2016-05-25 18:23         ` Ard Biesheuvel
2016-05-25 18:23           ` Ard Biesheuvel
     [not found]           ` <CAKv+Gu94GLWUJBCtNUDb4Jak3KL0-MGkUfk82fZ5UdwWH60P_w-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-05-26 10:56             ` Mark Rutland
2016-05-26 10:56               ` Mark Rutland
2016-06-03 15:50               ` Ard Biesheuvel
2016-06-03 15:50                 ` Ard Biesheuvel
2016-05-25 15:31   ` Catalin Marinas
2016-05-25 15:31     ` Catalin Marinas
2016-05-25 15:38   ` Jeremy Linton
2016-05-25 15:38     ` Jeremy Linton
2016-05-30 21:12   ` Matt Fleming
2016-05-30 21:12     ` Matt Fleming
     [not found]     ` <20160530211212.GG2984-mF/unelCI9GS6iBeEJttW/XRex20P6io@public.gmane.org>
2016-06-03 10:00       ` Will Deacon
2016-06-03 10:00         ` Will Deacon
     [not found]         ` <20160603100040.GJ9915-5wv7dgnIgG8@public.gmane.org>
2016-06-17 21:16           ` Matt Fleming [this message]
2016-06-17 21:16             ` Matt Fleming
     [not found]             ` <20160617211601.GN2658-mF/unelCI9GS6iBeEJttW/XRex20P6io@public.gmane.org>
2016-06-23 13:17               ` Mark Rutland
2016-06-23 13:17                 ` Mark Rutland

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=20160617211601.GN2658@codeblueprint.co.uk \
    --to=matt-mf/unelci9gs6ibeejttw/xrex20p6io@public.gmane.org \
    --cc=ard.biesheuvel-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org \
    --cc=catalin.marinas-5wv7dgnIgG8@public.gmane.org \
    --cc=jeremy.linton-5wv7dgnIgG8@public.gmane.org \
    --cc=leif.lindholm-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org \
    --cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
    --cc=linux-efi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=mark.rutland-5wv7dgnIgG8@public.gmane.org \
    --cc=will.deacon-5wv7dgnIgG8@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.