From: Olof Johansson <email@example.com> To: Pavel Machek <firstname.lastname@example.org> Cc: linux-arch <email@example.com>, Linux Kernel Mailing List <firstname.lastname@example.org>, ksummit <email@example.com> Subject: Re: [Ksummit-discuss] [TECH TOPIC] Planning code obsolescence Date: Mon, 10 Aug 2020 12:39:12 -0700 [thread overview] Message-ID: <CAOesGMjaJ=jcdBp7b-DfetUKKF+cC6NcJdHavBXyP49b9Bztwg@mail.gmail.com> (raw) In-Reply-To: <firstname.lastname@example.org> On Wed, Aug 5, 2020 at 12:30 PM Pavel Machek <email@example.com> wrote: > > On Wed 2020-08-05 20:50:43, Geert Uytterhoeven wrote: > > Hi Pavel, > > > > On Wed, Aug 5, 2020 at 7:26 PM Pavel Machek <firstname.lastname@example.org> wrote: > > > > I have submitted the below as a topic for the linux/arch/* MC that Mike > > > > and I run, but I suppose it also makes sense to discuss it on the > > > > ksummit-discuss mailing list (cross-posted to linux-arch and lkml) as well > > > > even if we don't discuss it at the main ksummit track. > > > > > > > * Latest kernel in which it was known to have worked > > > > > > For some old hardware, I started collecting kernel version, .config and dmesg from > > > successful boots. github.com/pavelmachek, click on "missy". > > > > You mean your complete hardware collection doesn't boot v5.8? ;-) > > I need to do some pushing, and yes, maybe some more testing. > > But I was wondering if someone sees this as useful and wants to > contribute more devices? :-). There's in my opinion a big difference between "the last user of this device sent it to Pavel and now it will be supported forever in spite of no users" and "there's a whole group of people using mainline on these old devices and Pavel makes sure it keeps booting for them". -Olof _______________________________________________ Ksummit-discuss mailing list Ksummitemail@example.com https://lists.linuxfoundation.org/mailman/listinfo/ksummit-discuss
next prev parent reply other threads:[~2020-08-10 19:39 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-07-31 15:00 Arnd Bergmann 2020-07-31 21:27 ` josh 2020-07-31 21:57 ` Bird, Tim 2020-07-31 22:47 ` josh 2020-08-05 17:26 ` Pavel Machek 2020-08-05 18:50 ` Geert Uytterhoeven 2020-08-05 19:30 ` Pavel Machek 2020-08-10 19:39 ` Olof Johansson [this message] 2020-08-16 12:53 ` Michael Ellerman
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='CAOesGMjaJ=jcdBp7b-DfetUKKF+cC6NcJdHavBXyP49b9Bztwg@mail.gmail.com' \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --subject='Re: [Ksummit-discuss] [TECH TOPIC] Planning code obsolescence' \ /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
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).