From: alex@shark-linux.de (Alexander Schulz)
To: linux-arm-kernel@lists.infradead.org
Subject: what about mach-shark?
Date: Mon, 02 Sep 2013 08:16:20 +0200 [thread overview]
Message-ID: <courier.52242D34.0000593F@shark-linux.de> (raw)
In-Reply-To: <CACRpkdappDnYfhR3XZQncUzhaBLiHw+8yu1gubJek=48CGghOQ@mail.gmail.com>
Hello,
I don't like it beeing deleted, but I do understand your concerns and if I
am honest to myself I will have to admit that I probably won't find the
time at least for this year.
Regards
Alexander
Linus Walleij writes:
> On Wed, Aug 28, 2013 at 11:05 AM, Alexander Schulz <alex@shark-linux.de> wrote:
>>> On Mon, Jul 4, 2011 at 10:08 PM, Nicolas Pitre <nico@fluxnic.net> wrote:
>>>
>>>> Is this used?
>>>
>>> This still goes unanswered after two years.
>>>
>>> Alexander, are you compiling and booting recent kernels on the Shark?
>>
>> Sorry, it must have slipped through somehow, I would have answered it if I
>> had seen it. I still have an eye on the list but haven't found the time to
>> really do anything with the shark in the recent time.
>
> Does this mean you will find that soon-ish, or can we delete the
> machine?
>
> Deletion is not definitive, it can be reverted by git revert if you find
> time to pick it up further down the road, we're mainly trying to
> avoid generic maintenance on machines that may not even
> boot.
>
> Yours,
> Linus Walleij
prev parent reply other threads:[~2013-09-02 6:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-04 20:08 what about mach-shark? Nicolas Pitre
2011-07-04 22:05 ` Russell King - ARM Linux
2011-07-04 22:20 ` Nicolas Pitre
2011-07-04 22:24 ` Russell King - ARM Linux
2011-07-05 1:51 ` Nicolas Pitre
2013-08-26 19:04 ` Linus Walleij
2013-08-26 19:06 ` Russell King - ARM Linux
2013-08-27 3:16 ` Linus Walleij
2013-08-28 9:05 ` Alexander Schulz
2013-08-28 11:53 ` Linus Walleij
2013-09-02 6:16 ` Alexander Schulz [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=courier.52242D34.0000593F@shark-linux.de \
--to=alex@shark-linux.de \
--cc=linux-arm-kernel@lists.infradead.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: 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;
as well as URLs for NNTP newsgroup(s).