Hi, On 06. 02. 20 20:39, Jean-Francois Dagenais wrote: > Hi Michal, > > Thanks for your very detailed answer before. Really appreciated. > > I fully understand that linux-xlnx on github is not meant as a community > project. I know there is nothing anyone can do anything about how github > works for now, but we all have to admit that the fact these repos are on open > GitHub, with the issues and merge-requests available surely suggest that they > are community open. It would be like renting a space in a shopping center, > filling it up with stuff, letting people come in and look around, keeping an > associate next to a cash register, but when people go up to the guys, he > would constantly have to say "I'm sorry, this is not really a store. You > can't purchase anything here."
A lot of project are using github just for publishing. There is Linux kernel also a lot of u-boot developers are using it because of connection to travis. It is up to every project to decide how this repo will be used. And I expect none is sending pull request via github to Linus. IIRC we have been checking disabling this functionality but it is simply something what it is not supported by github. These two projects are email based that's why we are using them. > It's no the biggest problem I'm sure, but until MRs and issues can be > disabled on GitHub, you will have submissions from passer-bys, confusion and > frustrations from "would-be" contributors. You *could* switch to gitlab.com > which already allows removing the issues and MR sections if I am not > mistaken. Just a thought. For me as a developer doesn't matter what should be used for publishing. It is out of my control and I still think we should have more aggressive upstreaming strategy to have things just there. The best would be not to have any soc vendor tree. >> On Feb 6, 2020, at 01:33, Michal Simek <[email protected]> wrote: >> >> Origin tree was composed from rebased v4.19 and that patchset is going >> forward. Even some other new patches haven't been added there but I >> expect that patches should be there. Please check that. > > I know you already took great care with your answers, really sorry, but this > is still not clear for me... > > So can we expect the same level of board functionality from linux-yocto as we > enjoy on linux-xlnx/2019.1 ? Xilinx testing team tests upstream kernel and linux-xlnx. I don't think that they test linux-yocto. As of today after initial work with Bruce Windriver is the main active contributor to these tree. And I expect it is tested by them. > And are you saying that whatever xilinx specific code is on linux-yocto now > and that is not in linus' tree will be maintained going forward on > linux-yocto? Unless something has changed there is going to be only one official Xilinx SoC vendor tree published via github. Maintenance will be done there, fixes will go there. There will be definitely communication how to sync linux-yocto with linux-xlnx but that will happen after publishing Xilinx v5.4 tree. I expect you know that linux-yocto maintainer (Bruce) works for Xilinx. > Correct this if it's wrong: I imagine one should track linux-xlnx together > with vivado/sdk/meta-xilinx-tools/petalinux releases, but use linux-yocto for > the open-source/meta-xilinx(only)/poky releases. linux-xlnx is primary tree for publishing changes done by Xilinx. If there is any fix which I am aware of which impact features used by Xilinx or affecting drivers/configurations/etc then I am taking them back to linux-xlnx. I am getting these patches from linux-yocto and also we are in CCs on mainline kernel. It means if you have any kernel patch please follow project rules and feel free to keep me in CC. Thanks, Michal -- Michal Simek, Ing. (M.Eng), OpenPGP -> KeyID: FE3D1F91 w: www.monstr.eu p: +42-0-721842854 Maintainer of Linux kernel - Xilinx Microblaze Maintainer of Linux kernel - Xilinx Zynq ARM and ZynqMP ARM64 SoCs U-Boot custodian - Xilinx Microblaze/Zynq/ZynqMP/Versal SoCs
signature.asc
Description: OpenPGP digital signature
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#4660): https://lists.yoctoproject.org/g/meta-xilinx/message/4660 Mute This Topic: https://lists.yoctoproject.org/mt/70987364/21656 Group Owner: [email protected] Unsubscribe: https://lists.yoctoproject.org/g/meta-xilinx/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
