public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Stafford Horne <shorne@gmail.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Openrisc <openrisc@lists.librecores.org>,
	LKML <linux-kernel@vger.kernel.org>
Subject: [GIT PULL] OpenRISC fixes for 5.19-rc5
Date: Wed, 6 Jul 2022 22:24:10 +0900	[thread overview]
Message-ID: <YsWM+im7pmU8MdeZ@antec> (raw)
In-Reply-To: <YsWMXAF3ePlWuxyF@antec>

Sorry, again with proper subject.

On Wed, Jul 06, 2022 at 10:21:32PM +0900, Stafford Horne wrote:
> Hi Linus,
> 
> Please consider for pull.
> 
> The following changes since commit 03c765b0e3b4cb5063276b086c76f7a612856a9a:
> 
>   Linux 5.19-rc4 (2022-06-26 14:22:10 -0700)
> 
> are available in the Git repository at:
> 
>   git@github.com:openrisc/linux.git tags/for-linus
> 
> for you to fetch changes up to 48bddb89d59eec27c3305d179b1832d5292e285d:
> 
>   openrisc: unwinder: Fix grammar issue in comment (2022-06-28 17:31:24 +0900)
> 
> ----------------------------------------------------------------
> OpenRISC fixes for 5.19-rc5
> 
> Fixups for OpenRISC found during recent testing:
>  - An OpenRISC irqchip fix to stop acking level interrupts which was
>    causing issues on SMP platforms.
>  - A comment typo fix in our unwinder code.
> 
> ----------------------------------------------------------------
> 
> Note, if you do check this against being in linux-next I dropped one patch from
> the linux next tree before creating this pull request.  The dropped patch was to
> add wireguard selftest support, but we decided against it as there are still
> some qemu bugs to workout before turning on wireguard selftests for OpenRISC.
> 
> Stafford Horne (1):
>       irqchip: or1k-pic: Undefine mask_ack for level triggered hardware
> 
> Xiang wangx (1):
>       openrisc: unwinder: Fix grammar issue in comment
> 
>  arch/openrisc/kernel/unwinder.c | 2 +-
>  drivers/irqchip/irq-or1k-pic.c  | 1 -
>  2 files changed, 1 insertion(+), 2 deletions(-)

  reply	other threads:[~2022-07-06 13:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-06 13:21 OpenRISC fixes for 5.19-rc5 Stafford Horne
2022-07-06 13:24 ` Stafford Horne [this message]
2022-07-06 18:12   ` [GIT PULL] " Linus Torvalds
2022-07-06 21:24     ` Stafford Horne

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=YsWM+im7pmU8MdeZ@antec \
    --to=shorne@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=openrisc@lists.librecores.org \
    --cc=torvalds@linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox