From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Petazzoni Date: Mon, 6 Jan 2020 10:42:48 +0100 Subject: [Buildroot] [PATCH] DEVELOPERS: add Nicholas Sielicki as contact for galileo_defconfig In-Reply-To: References: <20190811120739.26539-13-thomas.petazzoni@bootlin.com> <20191231152005.GH26395@scaer> <20200101163416.065d0ace@windsurf> <20200101161120.GL3519@scaer> <20200101211657.GP3519@scaer> <20200102091439.37998851@windsurf> <20200103092443.4e98511a@windsurf> Message-ID: <20200106104248.2fa99686@windsurf> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: buildroot@busybox.net Hello, On Mon, 6 Jan 2020 09:33:20 +0000 "Kinsella, Ray" wrote: > The Galileo had a nice niche as being one of the very few boards with PCIe. > Although it had been EOL'ed at Intel, I would get contacted about it regularly enough. > > Now there are alternatives such as the PINE64 etc, so that interest as dried up. > So yes, I think we should be agree'ing when we remove the defconfig. > > Presume the next buildroot LTS is 20.02, we I suppose gives us three choices. > > 1. EOL Galileo in 20.02 > 2. Update Galileo to support a latest Kernel LTS in 20.02 (with the compromises discussed previously). > 3. Leave Galileo as is for 20.02, and remove it post 20.02 release. > > When is code freeze for 20.02? End of January 2020. Best regards, Thomas -- Thomas Petazzoni, CTO, Bootlin Embedded Linux and Kernel engineering https://bootlin.com