Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: torvalds@linux-foundation.org
Cc: linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [GIT PULL] MIPS fixes for v6.0
Date: Wed, 21 Sep 2022 15:35:53 +0200	[thread overview]
Message-ID: <20220921133553.GA13191@alpha.franken.de> (raw)

The following changes since commit 80e78fcce86de0288793a0ef0f6acf37656ee4cf:

  Linux 6.0-rc5 (2022-09-11 16:22:01 -0400)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/mips/linux.git/ tags/mips-fixes_6.0_2

for you to fetch changes up to e9f3f8f488005f6da3cfb66070706770ecaef747:

  MIPS: Loongson32: Fix PHY-mode being left unspecified (2022-09-19 16:31:32 +0200)

----------------------------------------------------------------
- fix missing export for Lantiq watchdog driver
- fix ethernet phy interface setup for Loongson32

----------------------------------------------------------------
Randy Dunlap (1):
      MIPS: lantiq: export clk_get_io() for lantiq_wdt.ko

Serge Semin (1):
      MIPS: Loongson32: Fix PHY-mode being left unspecified

 arch/mips/lantiq/clk.c                 |  1 +
 arch/mips/loongson32/common/platform.c | 16 ++++++++--------
 2 files changed, 9 insertions(+), 8 deletions(-)

-- 
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea.                                                [ RFC1925, 2.3 ]

             reply	other threads:[~2022-09-21 13:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-21 13:35 Thomas Bogendoerfer [this message]
2022-09-21 16:34 ` [GIT PULL] MIPS fixes for v6.0 pr-tracker-bot
  -- strict thread matches above, loose matches on Subject: below --
2022-09-10 22:48 Thomas Bogendoerfer
2022-09-11 19:36 ` pr-tracker-bot

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=20220921133553.GA13191@alpha.franken.de \
    --to=tsbogend@alpha.franken.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@vger.kernel.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