All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jiri Slaby <jirislaby@gmail.com>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Nigel Cunningham <ncunningham@crca.org.au>,
	linux-pm <linux-pm@lists.linux-foundation.org>,
	LKML <linux-kernel@vger.kernel.org>,
	TuxOnIce-devel <tuxonice-devel@lists.tuxonice.net>
Subject: Re: What to do?
Date: Mon, 07 Sep 2009 12:06:58 +0200	[thread overview]
Message-ID: <4AA4DB42.1000800@gmail.com> (raw)
In-Reply-To: <200908240120.30776.rjw@sisk.pl>

Hi again.

On 08/24/2009 01:20 AM, Rafael J. Wysocki wrote:
> On Monday 24 August 2009, Nigel Cunningham wrote:
>> We should start by asking where you're at as far as knowledge of swsusp
>> and TuxOnIce goes. 

Well, I know swsups a bit and don't know about toi much. Still I think
it's not a problem at all. I learn quickly ;).

>> I know you've been around the TuxOnIce lists a bit,
>> but don't know how much you know about C programming or the inards of
>> the kernel, swsusp or TuxOnIce (ie how much help do you need to get up
>> to speed?).

I think C is no problem at all, so the kernel. The two I mentioned
above. I think I'll need no or low help from your side regarding the
code site. From what I've read already I would say it's well documented.

> Well, if you start from something that people don't like, it may be difficult
> to push the rest.
> 
> Still, I think Jiri is more than capable of handling that, so more or less
> everything that is a clear improvement and doesn't introduce regressions of any
> kind will probably work for me.

Thank you guys. I needed to cope with other things (a suspend
regression, writable /proc/<pid>/limits etc.) which took me a long time,
sorry.

Then I also went through the last "discussion" around the last merge try
mainly to see what others think about kernel-side implementation of
compression etc.

I hope I'll come up with something early.

Thanks.

  parent reply	other threads:[~2009-09-07 10:06 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-20  4:22 What to do? Nigel Cunningham
2009-08-20 15:24 ` Rafael J. Wysocki
2009-08-23 19:04   ` [TuxOnIce-devel] " Xavier Gnata
2009-08-24  4:33     ` Nigel Cunningham
2009-08-24  4:33     ` Nigel Cunningham
2009-08-23 19:04   ` Xavier Gnata
2009-08-20 15:24 ` Rafael J. Wysocki
2009-08-23 20:13 ` Jiri Slaby
2009-08-23 22:04   ` Rafael J. Wysocki
2009-08-23 23:07     ` Nigel Cunningham
2009-08-23 23:07     ` Nigel Cunningham
2009-08-23 23:20       ` Rafael J. Wysocki
2009-08-23 23:20       ` Rafael J. Wysocki
2009-09-07 10:06         ` Jiri Slaby
2009-09-07 10:06         ` Jiri Slaby [this message]
2009-08-23 22:04   ` Rafael J. Wysocki
2009-08-23 20:13 ` Jiri Slaby
  -- strict thread matches above, loose matches on Subject: below --
2009-08-20  4:22 Nigel Cunningham
2004-09-03 11:51 Андрiй Яремко
2004-09-03 12:16 ` Clemens Ladisch
2004-09-03 14:11   ` Jaroslav Kysela

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=4AA4DB42.1000800@gmail.com \
    --to=jirislaby@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@lists.linux-foundation.org \
    --cc=ncunningham@crca.org.au \
    --cc=rjw@sisk.pl \
    --cc=tuxonice-devel@lists.tuxonice.net \
    /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.