public inbox for linux-mips@vger.kernel.org
 help / color / mirror / Atom feed
From: Aleksander Jan Bajkowski <olek2@wp.pl>
To: john@phrozen.org, martin.blumenstingl@googlemail.com,
	hauke@hauke-m.de, tsbogend@alpha.franken.de, maz@kernel.org,
	linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: Aleksander Jan Bajkowski <olek2@wp.pl>
Subject: [PATCH v2 0/1] MIPS: lantiq: enable all hardware interrupts on second VPE
Date: Wed, 21 Sep 2022 22:59:43 +0200	[thread overview]
Message-ID: <20220921205944.466745-1-olek2@wp.pl> (raw)

v2:
 - switched to upstream recommendation.

Aleksander Jan Bajkowski (1):
  MIPS: lantiq: enable all hardware interrupts on second VPE

 arch/mips/lantiq/prom.c | 26 ++++++++++++++++++++++++--
 1 file changed, 24 insertions(+), 2 deletions(-)

-- 
2.30.2


             reply	other threads:[~2022-09-21 20:59 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-21 20:59 Aleksander Jan Bajkowski [this message]
2022-09-21 20:59 ` [PATCH v2 1/1] MIPS: lantiq: enable all hardware interrupts on second VPE Aleksander Jan Bajkowski
2022-09-24 10:45   ` Thomas Bogendoerfer

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=20220921205944.466745-1-olek2@wp.pl \
    --to=olek2@wp.pl \
    --cc=hauke@hauke-m.de \
    --cc=john@phrozen.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@vger.kernel.org \
    --cc=martin.blumenstingl@googlemail.com \
    --cc=maz@kernel.org \
    --cc=tsbogend@alpha.franken.de \
    /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