linux-mips.vger.kernel.org archive mirror
 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 v5.17
Date: Thu, 10 Feb 2022 11:29:39 +0100	[thread overview]
Message-ID: <20220210102939.GA9285@alpha.franken.de> (raw)

The following changes since commit dfd42facf1e4ada021b939b4e19c935dcdd55566:

  Linux 5.17-rc3 (2022-02-06 12:20:50 -0800)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/mips/linux.git/ tags/mips-fixes-5.17_3

for you to fetch changes up to d9565bf40da22426d2f660cb31700b6858d1911d:

  MIPS: DTS: CI20: fix how ddc power is enabled (2022-02-09 13:58:26 +0100)

----------------------------------------------------------------
- device tree fix for Ingenic CI20

----------------------------------------------------------------
H. Nikolaus Schaller (1):
      MIPS: DTS: CI20: fix how ddc power is enabled

 arch/mips/boot/dts/ingenic/ci20.dts | 15 ++-------------
 1 file changed, 2 insertions(+), 13 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-02-10 10:29 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-10 10:29 Thomas Bogendoerfer [this message]
2022-02-10 14:03 ` [GIT PULL] MIPS fixes for v5.17 pr-tracker-bot
  -- strict thread matches above, loose matches on Subject: below --
2022-03-03 16:48 Thomas Bogendoerfer
2022-03-03 19:18 ` pr-tracker-bot
2022-02-03  8:56 Thomas Bogendoerfer
2022-02-03 14:57 ` pr-tracker-bot
2022-01-28 13:33 Thomas Bogendoerfer
2022-01-28 17: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=20220210102939.GA9285@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;
as well as URLs for NNTP newsgroup(s).