From: Pavel Machek <pavel@ucw.cz>
To: Javier Romero <linux.kernel.programming@gmail.com>
Cc: Kamil Konieczny <k.konieczny@partner.samsung.com>,
Ken Moffat <zarniwhoop@ntlworld.com>,
linux-kernel@vger.kernel.org
Subject: Re: Contribution to Linux Kernel.
Date: Wed, 15 Nov 2017 11:40:19 +0100 [thread overview]
Message-ID: <20171115104019.GB456@amd> (raw)
In-Reply-To: <CAEH__nEMvScfyOanMUKrrQgq5PSueFhRoWM3YUd+3d2TSWyHWA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 606 bytes --]
Hi!
> Thank you for your answer.
>
> I've a Raspberry PI 3 and read that this device use it's own fork of the
> Linux Kernel.
> But do you think it would be useful to test linux-next on this device?
Well, if you can get linux-next working there, yes, that would be
nice. But this may be a bit too big task to start with.
But what I meant was running 32-bit linux-next on some spare
computer. Not enough people test that version...
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
next prev parent reply other threads:[~2017-11-15 10:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <59c7d4aa.d367370a.d4b44.16d6@mx.google.com>
[not found] ` <20170924202505.GA29877@milliways.localdomain>
2017-09-25 19:03 ` Contribution to Linux Kernel Javier Romero
2017-09-26 9:14 ` Kamil Konieczny
2017-09-26 14:52 ` Javier Romero
2017-10-23 9:29 ` Pavel Machek
2017-10-25 18:48 ` Javier Romero
[not found] ` <CAEH__nEMvScfyOanMUKrrQgq5PSueFhRoWM3YUd+3d2TSWyHWA@mail.gmail.com>
2017-11-15 10:40 ` Pavel Machek [this message]
2017-09-23 22:21 Javier Romero
[not found] <CGME20170922100216eucas1p240221e0bf388e43f463d12a0eec86941@eucas1p2.samsung.com>
2017-09-21 21:16 ` Javier Romero
2017-09-22 10:02 ` Kamil Konieczny
2017-09-22 12:51 ` Javier Romero
2017-09-22 19:15 ` Jonathan Corbet
2017-09-22 22:33 ` Javier Romero
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=20171115104019.GB456@amd \
--to=pavel@ucw.cz \
--cc=k.konieczny@partner.samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux.kernel.programming@gmail.com \
--cc=zarniwhoop@ntlworld.com \
/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 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.