From: Pavel Machek <firstname.lastname@example.org> To: Geert Uytterhoeven <email@example.com> Cc: linux-arch <firstname.lastname@example.org>, ksummit <email@example.com>, Linux Kernel Mailing List <firstname.lastname@example.org> Subject: Re: [Ksummit-discuss] [TECH TOPIC] Planning code obsolescence Date: Wed, 5 Aug 2020 21:30:01 +0200 [thread overview] Message-ID: <email@example.com> (raw) In-Reply-To: <CAMuHMdV20tZSu5gGsjf8h334+0xr1f=N9NvOoxHQGq42GYsj4g@mail.gmail.com> [-- Attachment #1.1: Type: text/plain, Size: 1052 bytes --] 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? :-). Pavel -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html [-- Attachment #1.2: signature.asc --] [-- Type: application/pgp-signature, Size: 195 bytes --] [-- Attachment #2: Type: text/plain, Size: 186 bytes --] _______________________________________________ Ksummit-discuss mailing list Ksummitemail@example.com https://lists.linuxfoundation.org/mailman/listinfo/ksummit-discuss
next prev parent reply other threads:[~2020-08-05 19:30 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 [this message] 2020-08-10 19:39 ` Olof Johansson 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 \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --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).