linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Nick Desaulniers <ndesaulniers@google.com>
To: Stefan Agner <stefan@agner.ch>
Cc: andrew@lunn.ch, mans@mansr.com, tony@atomide.com,
	Rob Herring <robh@kernel.org>,
	f.fainelli@gmail.com, gregory.clement@bootlin.com,
	Russell King <linux@armlinux.org.uk>,
	krzk@kernel.org, arm@kernel.org,
	bcm-kernel-feedback-list@broadcom.com,
	sebastian.hesselbarth@gmail.com, jason@lakedaemon.net,
	Arnd Bergmann <arnd@arndb.de>,
	Marc Gonzalez <marc.w.gonzalez@free.fr>,
	rjui@broadcom.com, ssantosh@kernel.org,
	Linux ARM <linux-arm-kernel@lists.infradead.org>,
	sbranden@broadcom.com, Ard Biesheuvel <ard.biesheuvel@linaro.org>,
	nico@fluxnic.net, LKML <linux-kernel@vger.kernel.org>,
	kgene@kernel.org, Olof Johansson <olof@lixom.net>,
	Robin Murphy <robin.murphy@arm.com>
Subject: Re: [PATCH v4 2/2] ARM: OMAP2: drop explicit assembler architecture
Date: Thu, 30 May 2019 13:02:48 -0700	[thread overview]
Message-ID: <CAKwvOdmsHxyPU2O1vZ-Mah-E5vTtEWKHStp2EQCiE4A55D8xDQ@mail.gmail.com> (raw)
In-Reply-To: <5ead0fe96f7e5729e4a82f432022b16cb84458a6.1558996564.git.stefan@agner.ch>

On Mon, May 27, 2019 at 3:41 PM Stefan Agner <stefan@agner.ch> wrote:
>
> OMAP2 depends on ARCH_MULTI_V6, which makes sure that the kernel is
> compiled with -march=armv6. The compiler frontend will pass the
> architecture to the assembler. There is no explicit architecture
> specification necessary.
>
> Signed-off-by: Stefan Agner <stefan@agner.ch>
> Acked-by: Tony Lindgren <tony@atomide.com>
> ---
> Changes since v2:
> - New patch
>
> Changes since v3:
> - Rebase on top of v5.2-rc2

Hi Stefan, looks like both patches are ack'd.  Are you waiting for an
explicit reviewed by tag to submit to
https://www.armlinux.org.uk/developer/patches/?

-- 
Thanks,
~Nick Desaulniers

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2019-05-30 20:03 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-27 22:40 [PATCH v4 1/2] ARM: use arch_extension directive instead of arch argument Stefan Agner
2019-05-27 22:40 ` [PATCH v4 2/2] ARM: OMAP2: drop explicit assembler architecture Stefan Agner
2019-05-30 20:02   ` Nick Desaulniers [this message]
2019-06-02 16:35     ` Stefan Agner
2019-06-19 17:34   ` Olof Johansson
2019-06-05 19:05 ` [PATCH v4 1/2] ARM: use arch_extension directive instead of arch argument Florian Fainelli
2019-06-19 17:33 ` Olof Johansson

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=CAKwvOdmsHxyPU2O1vZ-Mah-E5vTtEWKHStp2EQCiE4A55D8xDQ@mail.gmail.com \
    --to=ndesaulniers@google.com \
    --cc=andrew@lunn.ch \
    --cc=ard.biesheuvel@linaro.org \
    --cc=arm@kernel.org \
    --cc=arnd@arndb.de \
    --cc=bcm-kernel-feedback-list@broadcom.com \
    --cc=f.fainelli@gmail.com \
    --cc=gregory.clement@bootlin.com \
    --cc=jason@lakedaemon.net \
    --cc=kgene@kernel.org \
    --cc=krzk@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=mans@mansr.com \
    --cc=marc.w.gonzalez@free.fr \
    --cc=nico@fluxnic.net \
    --cc=olof@lixom.net \
    --cc=rjui@broadcom.com \
    --cc=robh@kernel.org \
    --cc=robin.murphy@arm.com \
    --cc=sbranden@broadcom.com \
    --cc=sebastian.hesselbarth@gmail.com \
    --cc=ssantosh@kernel.org \
    --cc=stefan@agner.ch \
    --cc=tony@atomide.com \
    /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;
as well as URLs for NNTP newsgroup(s).