All of lore.kernel.org
 help / color / mirror / Atom feed
From: "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>
To: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Cc: "stable@vger.kernel.org" <stable@vger.kernel.org>,
	stable-commits@vger.kernel.org
Subject: Re: Patch "arm64: mm: use correct mapping granularity under DEBUG_RODATA" has been added to the 4.1-stable tree
Date: Sun, 31 Jan 2016 11:22:04 -0800	[thread overview]
Message-ID: <20160131192204.GE23698@kroah.com> (raw)
In-Reply-To: <CAKv+Gu-2KK=PS+4bUrJ_iGmTkc0UTCtjWqQ828R=vBW6N_nxpg@mail.gmail.com>

On Thu, Jan 28, 2016 at 09:18:26AM +0100, Ard Biesheuvel wrote:
> On 27 January 2016 at 07:54,  <gregkh@linuxfoundation.org> wrote:
> >
> > This is a note to let you know that I've just added the patch titled
> >
> >     arm64: mm: use correct mapping granularity under DEBUG_RODATA
> >
> > to the 4.1-stable tree which can be found at:
> >     http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
> >
> > The filename of the patch is:
> >      arm64-mm-use-correct-mapping-granularity-under-debug_rodata.patch
> > and it can be found in the queue-4.1 subdirectory.
> >
> > If you, or anyone else, feels it should not be added to the stable tree,
> > please let <stable@vger.kernel.org> know about it.
> >
> 
> Apologies for the late notice: as mentioned in the other thread, this
> will fail to build due to a missing #define of SWAPPER_BLOCK_SIZE. I
> will submit a new version specific to -stable (which just adds the
> #define locally)

Now dropped, and I'll pick this up for the next round of kernels.

thanks,

greg k-h-

      reply	other threads:[~2016-01-31 19:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-27  6:54 Patch "arm64: mm: use correct mapping granularity under DEBUG_RODATA" has been added to the 4.1-stable tree gregkh
2016-01-28  8:18 ` Ard Biesheuvel
2016-01-31 19:22   ` gregkh [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=20160131192204.GE23698@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=ard.biesheuvel@linaro.org \
    --cc=stable-commits@vger.kernel.org \
    --cc=stable@vger.kernel.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.