From: Vinod Koul <vkoul@kernel.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Kishon Vijay Abraham I <kishon@ti.com>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Anurag Kumar Vulisha <anurag.kumar.vulisha@xilinx.com>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Hyun Kwon <hyun.kwon@xilinx.com>,
Michal Simek <michal.simek@xilinx.com>
Subject: Re: linux-next: manual merge of the dmaengine tree with the phy-next tree
Date: Tue, 21 Jul 2020 12:45:04 +0530 [thread overview]
Message-ID: <20200721071504.GK12965@vkoul-mobl> (raw)
In-Reply-To: <20200721161701.64b4245e@canb.auug.org.au>
Hi Stephen,
On 21-07-20, 16:17, Stephen Rothwell wrote:
> Hi all,
>
> Today's linux-next merge of the dmaengine tree got a conflict in:
>
> MAINTAINERS
>
> between commit:
>
> 4a33bea00314 ("phy: zynqmp: Add PHY driver for the Xilinx ZynqMP Gigabit Transceiver")
>
> from the phy-next tree and commit:
>
> ef9303fdf46f ("dt: bindings: dma: xilinx: dpdma: DT bindings for Xilinx DPDMA")
>
> from the dmaengine tree.
Thanks the fix looks okay.
> I fixed it up (see below) and can carry the fix as necessary. This
> is now fixed as far as linux-next is concerned, but any non trivial
> conflicts should be mentioned to your upstream maintainer when your tree
> is submitted for merging. You may also want to consider cooperating
> with the maintainer of the conflicting tree to minimise any particularly
> complex conflicts.
>
> --
> Cheers,
> Stephen Rothwell
>
> diff --cc MAINTAINERS
> index 495e4247cbb0,1ba09904354f..000000000000
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@@ -11432,20 -11364,14 +11434,13 @@@ L: linux-arm-kernel@lists.infradead.or
> S: Supported
> F: drivers/usb/gadget/udc/atmel_usba_udc.*
>
> -MICROSEMI ETHERNET SWITCH DRIVER
> -M: Alexandre Belloni <alexandre.belloni@bootlin.com>
> -M: Microchip Linux Driver Support <UNGLinuxDriver@microchip.com>
> -L: netdev@vger.kernel.org
> +MICROCHIP WILC1000 WIFI DRIVER
> +M: Ajay Singh <ajay.kathat@microchip.com>
> +M: Claudiu Beznea <claudiu.beznea@microchip.com>
> +L: linux-wireless@vger.kernel.org
> S: Supported
> -F: drivers/net/ethernet/mscc/
> -F: include/soc/mscc/ocelot*
> +F: drivers/net/wireless/microchip/wilc1000/
>
> - MICROCHIP XDMA DRIVER
> - M: Ludovic Desroches <ludovic.desroches@microchip.com>
> - L: linux-arm-kernel@lists.infradead.org
> - L: dmaengine@vger.kernel.org
> - S: Supported
> - F: drivers/dma/at_xdmac.c
> -
> MICROSEMI MIPS SOCS
> M: Alexandre Belloni <alexandre.belloni@bootlin.com>
> M: Microchip Linux Driver Support <UNGLinuxDriver@microchip.com>
> @@@ -18990,15 -18847,15 +18985,24 @@@ F: Documentation/devicetree/bindings/me
> F: drivers/media/platform/xilinx/
> F: include/uapi/linux/xilinx-v4l2-controls.h
>
> +XILINX ZYNQMP PSGTR PHY DRIVER
> +M: Anurag Kumar Vulisha <anurag.kumar.vulisha@xilinx.com>
> +M: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
> +L: linux-kernel@vger.kernel.org
> +S: Supported
> +T: git https://github.com/Xilinx/linux-xlnx.git
> +F: Documentation/devicetree/bindings/phy/xlnx,zynqmp-psgtr.yaml
> +F: drivers/phy/xilinx/phy-zynqmp.c
> +
> + XILINX ZYNQMP DPDMA DRIVER
> + M: Hyun Kwon <hyun.kwon@xilinx.com>
> + M: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
> + L: dmaengine@vger.kernel.org
> + S: Supported
> + F: Documentation/devicetree/bindings/dma/xilinx/xlnx,zynqmp-dpdma.yaml
> + F: drivers/dma/xilinx/xilinx_dpdma.c
> + F: include/dt-bindings/dma/xlnx-zynqmp-dpdma.h
> +
> XILLYBUS DRIVER
> M: Eli Billauer <eli.billauer@gmail.com>
> L: linux-kernel@vger.kernel.org
--
~Vinod
prev parent reply other threads:[~2020-07-21 7:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-21 6:17 linux-next: manual merge of the dmaengine tree with the phy-next tree Stephen Rothwell
2020-07-21 7:15 ` Vinod Koul [this message]
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=20200721071504.GK12965@vkoul-mobl \
--to=vkoul@kernel.org \
--cc=anurag.kumar.vulisha@xilinx.com \
--cc=hyun.kwon@xilinx.com \
--cc=kishon@ti.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=michal.simek@xilinx.com \
--cc=sfr@canb.auug.org.au \
/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