soc.lore.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dinh Nguyen <dinguyen@kernel.org>
To: arm@kernel.org, soc@kernel.org
Cc: dinguyen@kernel.org
Subject: [GIT PULL 2/2] arm64: dts: socfpga: dts updates for v5.17, part 2
Date: Fri, 11 Feb 2022 05:25:56 -0600	[thread overview]
Message-ID: <20220211112556.98940-2-dinguyen@kernel.org> (raw)
In-Reply-To: <20220211112556.98940-1-dinguyen@kernel.org>

The following changes since commit e783362eb54cd99b2cac8b3a9aeac942e6f6ac07:

  Linux 5.17-rc1 (2022-01-23 10:12:53 +0200)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/dinguyen/linux.git tags/socfpga_dts_update_for_v5.18_part2

for you to fetch changes up to 268a491aebc25e6dc7c618903b09ac3a2e8af530:

  arm64: dts: agilex: use the compatible "intel,socfpga-agilex-hsotg" (2022-02-09 13:18:48 -0600)

----------------------------------------------------------------
SoCFPGA dts updates for v5.18, part 2
- Add the "intel,socfpga-agilex-hsotg" compatible for Agilex platform

----------------------------------------------------------------
Dinh Nguyen (2):
      dt-bindings: usb: dwc2: add compatible "intel,socfpga-agilex-hsotg"
      arm64: dts: agilex: use the compatible "intel,socfpga-agilex-hsotg"

 Documentation/devicetree/bindings/usb/dwc2.yaml | 1 +
 arch/arm64/boot/dts/intel/socfpga_agilex.dtsi   | 4 ++--
 2 files changed, 3 insertions(+), 2 deletions(-)

  reply	other threads:[~2022-02-11 11:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-11 11:25 [GIT PULL 1/2] ARM: dts: socfpga: dts bindings cleanup for v5.18, part 1 Dinh Nguyen
2022-02-11 11:25 ` Dinh Nguyen [this message]
2022-02-13  1:08   ` [GIT PULL 2/2] arm64: dts: socfpga: dts updates for v5.17, part 2 Dinh Nguyen
2022-02-18 20:40 ` [GIT PULL 1/2] ARM: dts: socfpga: dts bindings cleanup for v5.18, part 1 patchwork-bot+linux-soc
2022-02-25 17:21 ` patchwork-bot+linux-soc

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=20220211112556.98940-2-dinguyen@kernel.org \
    --to=dinguyen@kernel.org \
    --cc=arm@kernel.org \
    --cc=soc@kernel.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).