public inbox for openbmc@ozlabs.org
 help / color / mirror / Atom feed
From: Andrew Jeffery <andrew@codeconstruct.com.au>
To: openbmc <openbmc@lists.ozlabs.org>
Cc: Joel Stanley <joel@jms.id.au>
Subject: Experimental openbmc/linux dev-6.17 branch
Date: Mon, 17 Nov 2025 17:24:04 +1030	[thread overview]
Message-ID: <93dc30c9e93d5d99dc75f0bce87459bf03755064.camel@codeconstruct.com.au> (raw)

Hi everyone,

Just a quick note that I've put together an experimental dev-6.17
branch and pushed it to openbmc/linux. This is largely in preparation
for the next LTS release, whenever that comes.

At the time of this email I haven't done any further integration work.
However, for the record, here are the patches that were changed or
dropped with respect to dev-6.12:

   Amit Sunil Dhamne (1):
         usb: typec: tcpm: Add support for parsing pd-revision DT property
   
   Andrew Jeffery (2):
         soc: aspeed: lpc-snoop: Rearrange channel paths
         soc: aspeed: lpc-snoop: Lift channel config to const structs
   
   Breno Leitao (1):
         Revert "x86/bugs: Make spectre user default depend on MITIGATION_SPECTRE_V2" on v6.6 and older
   
   Cosmo Chou (1):
         dt-bindings: trivial-devices: add mps,mp5998
   
   Eddie James (3):
         leds: pca955x: Optimize probe led selection
         leds: pca955x: Add HW blink support
         leds: Ensure hardware blinking turns off when requested
   
   Jeremy Kerr (2):
         net: mctp: Add MCTP USB transport driver
         net: mctp: separate routing database from routing operations
   
   Leo Yang (1):
         hwmon: Add driver for TI INA233 Current and Power Monitor
   
   Peter Yin (1):
         dt-bindings: trivial-devices: add isil,isl69260
   
   Tomer Maimon (2):
         reset: npcm: register npcm8xx clock auxiliary bus device
         clk: npcm8xx: add clock controller
   
   Wensheng Wang (1):
         dt-bindings: hwmon: Add MPS mp2869,mp29608,mp29612,mp29816 and mp29502

Cheers,

Andrew


                 reply	other threads:[~2025-11-17  6:54 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=93dc30c9e93d5d99dc75f0bce87459bf03755064.camel@codeconstruct.com.au \
    --to=andrew@codeconstruct.com.au \
    --cc=joel@jms.id.au \
    --cc=openbmc@lists.ozlabs.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