All of lore.kernel.org
 help / color / mirror / Atom feed
diff for duplicates of <DG8QBWSJ79MP.2MVIHFRBX3WXX@linux.dev>

diff --git a/a/1.txt b/N1/1.txt
index dbbaf20..5a9e41e 100644
--- a/a/1.txt
+++ b/N1/1.txt
@@ -127,7 +127,7 @@ phy-stm32-usbphyc.c and phy-rockchip-usb.c) is the standard method.
 I would not insist on the "onboard_usb_dev managed vbus" if this patch
 (PHY managed) is considered proper way.
 
--- 
-linux-phy mailing list
-linux-phy@lists.infradead.org
-https://lists.infradead.org/mailman/listinfo/linux-phy
+_______________________________________________
+linux-riscv mailing list
+linux-riscv@lists.infradead.org
+http://lists.infradead.org/mailman/listinfo/linux-riscv
diff --git a/a/content_digest b/N1/content_digest
index 93f9003..18ce882 100644
--- a/a/content_digest
+++ b/N1/content_digest
@@ -150,9 +150,9 @@
  "I would not insist on the \"onboard_usb_dev managed vbus\" if this patch\n"
  "(PHY managed) is considered proper way.\n"
  "\n"
- "-- \n"
- "linux-phy mailing list\n"
- "linux-phy@lists.infradead.org\n"
- https://lists.infradead.org/mailman/listinfo/linux-phy
+ "_______________________________________________\n"
+ "linux-riscv mailing list\n"
+ "linux-riscv@lists.infradead.org\n"
+ http://lists.infradead.org/mailman/listinfo/linux-riscv
 
-ef4210cacf45c7feb2410b482b8bd7d4e8824038ead45fc0620515b039f151b9
+d3e3488b53f257bac5e0f6c759218d76b6cd4f195f2265dba31dde3f9d491f58

diff --git a/a/1.txt b/N2/1.txt
index dbbaf20..b634c30 100644
--- a/a/1.txt
+++ b/N2/1.txt
@@ -126,8 +126,3 @@ I am not certain if managing VBUS in the PHY driver (e.g.,
 phy-stm32-usbphyc.c and phy-rockchip-usb.c) is the standard method.
 I would not insist on the "onboard_usb_dev managed vbus" if this patch
 (PHY managed) is considered proper way.
-
--- 
-linux-phy mailing list
-linux-phy@lists.infradead.org
-https://lists.infradead.org/mailman/listinfo/linux-phy
diff --git a/a/content_digest b/N2/content_digest
index 93f9003..b3cffed 100644
--- a/a/content_digest
+++ b/N2/content_digest
@@ -148,11 +148,6 @@
  "I am not certain if managing VBUS in the PHY driver (e.g.,\n"
  "phy-stm32-usbphyc.c and phy-rockchip-usb.c) is the standard method.\n"
  "I would not insist on the \"onboard_usb_dev managed vbus\" if this patch\n"
- "(PHY managed) is considered proper way.\n"
- "\n"
- "-- \n"
- "linux-phy mailing list\n"
- "linux-phy@lists.infradead.org\n"
- https://lists.infradead.org/mailman/listinfo/linux-phy
+ (PHY managed) is considered proper way.
 
-ef4210cacf45c7feb2410b482b8bd7d4e8824038ead45fc0620515b039f151b9
+89fe67466ced03b03771c8c490f6e9fe6849b7b967aee81cf752b9bedf526e35

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.