From: Tony Lindgren <tony@atomide.com>
To: Ard Biesheuvel <ardb@kernel.org>
Cc: Stefan Agner <stefan@agner.ch>,
linux-omap@vger.kernel.org,
Nick Desaulniers <ndesaulniers@google.com>,
LKML <linux-kernel@vger.kernel.org>,
Peter Smith <Peter.Smith@arm.com>,
clang-built-linux <clang-built-linux@googlegroups.com>,
Russell King <linux@armlinux.org.uk>, nd <nd@arm.com>,
Linux ARM <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] ARM: OMAP2+: drop unnecessary adrl
Date: Fri, 17 Apr 2020 08:23:34 -0700 [thread overview]
Message-ID: <20200417152334.GN37466@atomide.com> (raw)
In-Reply-To: <CAMj1kXEe835GbXU5qgX-QQ5n4SmwQO1nAoAZw5pUVCbR=J8XmQ@mail.gmail.com>
* Ard Biesheuvel <ardb@kernel.org> [200402 14:37]:
> On Thu, 2 Apr 2020 at 16:34, Stefan Agner <stefan@agner.ch> wrote:
> > Just to confirm: The instance at hand today seems to be working fine
> > without adrl, so I guess we are fine here, do you agree?
> >
>
> I agree. Apologies for hijacking the thread :-)
Yes this seems to work just fine based on a quick test, will
be applying for v5.8.
Thanks,
Tony
WARNING: multiple messages have this Message-ID (diff)
From: Tony Lindgren <tony@atomide.com>
To: Ard Biesheuvel <ardb@kernel.org>
Cc: nd <nd@arm.com>, Nick Desaulniers <ndesaulniers@google.com>,
LKML <linux-kernel@vger.kernel.org>,
Stefan Agner <stefan@agner.ch>, Peter Smith <Peter.Smith@arm.com>,
clang-built-linux <clang-built-linux@googlegroups.com>,
Russell King <linux@armlinux.org.uk>,
linux-omap@vger.kernel.org,
Linux ARM <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] ARM: OMAP2+: drop unnecessary adrl
Date: Fri, 17 Apr 2020 08:23:34 -0700 [thread overview]
Message-ID: <20200417152334.GN37466@atomide.com> (raw)
In-Reply-To: <CAMj1kXEe835GbXU5qgX-QQ5n4SmwQO1nAoAZw5pUVCbR=J8XmQ@mail.gmail.com>
* Ard Biesheuvel <ardb@kernel.org> [200402 14:37]:
> On Thu, 2 Apr 2020 at 16:34, Stefan Agner <stefan@agner.ch> wrote:
> > Just to confirm: The instance at hand today seems to be working fine
> > without adrl, so I guess we are fine here, do you agree?
> >
>
> I agree. Apologies for hijacking the thread :-)
Yes this seems to work just fine based on a quick test, will
be applying for v5.8.
Thanks,
Tony
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2020-04-17 15:23 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-29 20:33 [PATCH] ARM: OMAP2+: drop unnecessary adrl Stefan Agner
2020-03-29 20:33 ` Stefan Agner
2020-04-01 18:02 ` Nick Desaulniers
2020-04-01 18:02 ` Nick Desaulniers
2020-04-02 9:48 ` Ard Biesheuvel
2020-04-02 9:48 ` Ard Biesheuvel
2020-04-02 11:50 ` Peter Smith
2020-04-02 11:50 ` Peter Smith
2020-04-02 12:05 ` Ard Biesheuvel
2020-04-02 12:05 ` Ard Biesheuvel
2020-04-02 14:34 ` Stefan Agner
2020-04-02 14:34 ` Stefan Agner
2020-04-02 14:36 ` Ard Biesheuvel
2020-04-02 14:36 ` Ard Biesheuvel
2020-04-17 15:23 ` Tony Lindgren [this message]
2020-04-17 15:23 ` Tony Lindgren
2020-04-02 17:50 ` Peter Smith
2020-04-02 17:50 ` Peter Smith
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=20200417152334.GN37466@atomide.com \
--to=tony@atomide.com \
--cc=Peter.Smith@arm.com \
--cc=ardb@kernel.org \
--cc=clang-built-linux@googlegroups.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=nd@arm.com \
--cc=ndesaulniers@google.com \
--cc=stefan@agner.ch \
/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.