Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] DEVELOPERS: add Nicholas Sielicki as contact for galileo_defconfig
Date: Mon, 6 Jan 2020 10:42:48 +0100	[thread overview]
Message-ID: <20200106104248.2fa99686@windsurf> (raw)
In-Reply-To: <BN6PR11MB4145527DD926BC273CA3F6B7903C0@BN6PR11MB4145.namprd11.prod.outlook.com>

Hello,

On Mon, 6 Jan 2020 09:33:20 +0000
"Kinsella, Ray" <ray.kinsella@intel.com> 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

      parent reply	other threads:[~2020-01-06  9:42 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-11 12:07 [Buildroot] [PATCH] DEVELOPERS: add Nicholas Sielicki as contact for galileo_defconfig Thomas Petazzoni
2019-12-31 15:20 ` Yann E. MORIN
     [not found]   ` <BN6PR11MB4145284497C2AF782D307B3590260@BN6PR11MB4145.namprd11.prod.outlook.com>
2020-01-01  9:08     ` Yann E. MORIN
     [not found]   ` <MN2PR11MB4160005AC798211088F160C090210@MN2PR11MB4160.namprd11.prod.outlook.com>
2020-01-01 15:34     ` Thomas Petazzoni
2020-01-01 16:11       ` Yann E. MORIN
     [not found]         ` <BN6PR11MB4145B63CE33025809CB99F8490210@BN6PR11MB4145.namprd11.prod.outlook.com>
2020-01-01 21:16           ` Yann E. MORIN
2020-01-02  8:14             ` Thomas Petazzoni
     [not found]               ` <BN6PR11MB4145CB3739932D59E074FC1C90200@BN6PR11MB4145.namprd11.prod.outlook.com>
2020-01-03  8:24                 ` Thomas Petazzoni
     [not found]                   ` <BN6PR11MB4145527DD926BC273CA3F6B7903C0@BN6PR11MB4145.namprd11.prod.outlook.com>
2020-01-06  9:42                     ` Thomas Petazzoni [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=20200106104248.2fa99686@windsurf \
    --to=thomas.petazzoni@bootlin.com \
    --cc=buildroot@busybox.net \
    /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