From: Pavel Machek <pavel@ucw.cz> To: Arnd Bergmann <arnd@arndb.de> Cc: linux-arch <linux-arch@vger.kernel.org>, Linux Kernel Mailing List <linux-kernel@vger.kernel.org>, ksummit <ksummit-discuss@lists.linuxfoundation.org> Subject: Re: [Ksummit-discuss] [TECH TOPIC] Planning code obsolescence Date: Wed, 5 Aug 2020 19:26:30 +0200 [thread overview] Message-ID: <20200805172629.GA1040@bug> (raw) In-Reply-To: <CAK8P3a2PK_bC5=3wcWm43=y5xk-Dq5-fGPExJMnOrNfGfB1m1A@mail.gmail.com> Hi! > 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". Best regards, Pavel (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html _______________________________________________ Ksummit-discuss mailing list Ksummit-discuss@lists.linuxfoundation.org https://lists.linuxfoundation.org/mailman/listinfo/ksummit-discuss
WARNING: multiple messages have this Message-ID (diff)
From: Pavel Machek <pavel@ucw.cz> To: Arnd Bergmann <arnd@arndb.de> Cc: ksummit <ksummit-discuss@lists.linuxfoundation.org>, Mike Rapoport <rppt@linux.ibm.com>, linux-arch <linux-arch@vger.kernel.org>, Linux Kernel Mailing List <linux-kernel@vger.kernel.org> Subject: Re: [TECH TOPIC] Planning code obsolescence Date: Wed, 5 Aug 2020 19:26:30 +0200 [thread overview] Message-ID: <20200805172629.GA1040@bug> (raw) In-Reply-To: <CAK8P3a2PK_bC5=3wcWm43=y5xk-Dq5-fGPExJMnOrNfGfB1m1A@mail.gmail.com> Hi! > 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". Best regards, Pavel (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next prev parent reply other threads:[~2020-08-05 17:26 UTC|newest] Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-07-31 15:00 [Ksummit-discuss] [TECH TOPIC] Planning code obsolescence Arnd Bergmann 2020-07-31 15:00 ` Arnd Bergmann 2020-07-31 21:27 ` [Ksummit-discuss] " josh 2020-07-31 21:27 ` josh 2020-07-31 21:57 ` Bird, Tim 2020-07-31 21:57 ` Bird, Tim 2020-07-31 22:47 ` josh 2020-07-31 22:47 ` josh 2020-08-05 17:26 ` Pavel Machek [this message] 2020-08-05 17:26 ` Pavel Machek 2020-08-05 18:50 ` [Ksummit-discuss] " Geert Uytterhoeven 2020-08-05 18:50 ` Geert Uytterhoeven 2020-08-05 19:30 ` Pavel Machek 2020-08-05 19:30 ` Pavel Machek 2020-08-10 19:39 ` Olof Johansson 2020-08-10 19:39 ` Olof Johansson 2020-08-16 12:53 ` Michael Ellerman 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=20200805172629.GA1040@bug \ --to=pavel@ucw.cz \ --cc=arnd@arndb.de \ --cc=ksummit-discuss@lists.linuxfoundation.org \ --cc=linux-arch@vger.kernel.org \ --cc=linux-kernel@vger.kernel.org \ /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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.