From: mcsim.planeta@gmail.com (Maksym Planeta)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Gsoc participation
Date: Mon, 14 Mar 2011 17:36:56 +0200 [thread overview]
Message-ID: <1300117016.28755.27.camel@debian> (raw)
In-Reply-To: <AANLkTimsHbSX6cM7XxJBheeuCob8pEA9dcuPKCk2vmhH@mail.gmail.com>
On Mon, 14/03/2011 at 16:29 +0200, Daniel Baluta wrote:
> What about making kmemleak [1] available on not yet supported architectures?
This sounds interesting.
There was written that
> Only the ARM and x86 architectures are currently supported.
Does it mean that there isn't support for x86_64 architecture?
Thanks,
--
Maksym Planeta <mcsim.planeta@gmail.com>
next prev parent reply other threads:[~2011-03-14 15:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-13 21:44 Gsoc participation Maksym Planeta
2011-03-13 23:28 ` Greg KH
2011-03-14 14:19 ` Maksym Planeta
2011-03-14 14:29 ` Daniel Baluta
2011-03-14 15:36 ` Maksym Planeta [this message]
2011-03-14 15:46 ` Javier Martinez Canillas
2011-03-14 16:06 ` Denis Kirjanov
2011-03-14 14:39 ` Greg KH
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=1300117016.28755.27.camel@debian \
--to=mcsim.planeta@gmail.com \
--cc=kernelnewbies@lists.kernelnewbies.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).