From: Hans Reiser <reiser@namesys.com>
To: David Masover <jedi@ninja.dynup.net>
Cc: reiserfs-list@namesys.com, vs@thebsh.namesys.com
Subject: Re: swsusp and reiser4
Date: Sat, 13 Dec 2003 11:19:30 +0300 [thread overview]
Message-ID: <3FDACB92.3030304@namesys.com> (raw)
In-Reply-To: <3FDAA5BB.6090307@ninja.dynup.net>
David Masover wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Reiser4 won't compile with the latest swsusp patches. According to
> Nigel Cunningham,
>
> > Regarding Reiser4, PF_IOTHREAD should be replaced by PF_SYNCTHREAD.
>
> The swsusp patches actually go so far as to remove the line defining
> PF_IOTHREAD. Nigel says he's working on it, but I want to make sure
> there's cooperation (or at least acknowledgement) at this end.
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.2.3 (GNU/Linux)
> Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
>
> iQIVAwUBP9qluwisZLIF6uqOAQJ94A/+MmyDnCF/7Ejv+aHNkk2fI7KLXsOgV/dp
> S/Jos0ajG7CwJh2ClwT7UryaMlJflf80anfslw9w6I/7o56GMShfCB1RgkaHe/zm
> S77Ul7Si22W2YLsEQxJ/JpIQWNrc/p6LiiySA6DBE8IxLYrjB+tFFJnwcV6sqVij
> Lv3MjuJ7YBgZubQMOtUgydElhb0M06LGpm2RU+k9pOSxrrVSzAwe2fRc7gBe+KrJ
> SZsN2DXqYBrhoCqopPnsyD7EwcIe41IUR2OssMASRJXTTdue+9xg4QVb/2GEnkM8
> N4WaaoiBQNvYptRMLe8zbNMrTJZZ54VykHdJVz/fbutkZGIMdONgWCTNHUsosTz9
> 0Ry4difeTSc30W419oDhYG64TLAnP+ux4ORdIIisxBlKB6ZAsvb3HsCWDRPFfClZ
> JRz24MPcrgiu4XrBJOiT1dIOcCAVs4w5BDZdm6ta9AI2H8KUxb9eUF83DXgQT9Qu
> olrQgM71faxXTy2lVadxxM+HbEdpS7fApWZOJFdGw9HnmIjJZf0giTPzA83xxHxI
> zkXJkVkCvTJR24V48CcNbue9+ukz57kMgEJqXiwy3YQk45nckXatX56HkOeF5dlW
> zqTlA2yCTaISp33u0tXp61MXjQT+j6URsjTN4dxZ5zLQDLdVdoTSuYlW1zihO0aT
> zWAOnGUMPIE=
> =0JZu
> -----END PGP SIGNATURE-----
>
>
>
thank you kindly, Vladimir will look into it.
--
Hans
next prev parent reply other threads:[~2003-12-13 8:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-13 5:38 swsusp and reiser4 David Masover
2003-12-13 8:19 ` Hans Reiser [this message]
2003-12-15 10:19 ` Vladimir Saveliev
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=3FDACB92.3030304@namesys.com \
--to=reiser@namesys.com \
--cc=jedi@ninja.dynup.net \
--cc=reiserfs-list@namesys.com \
--cc=vs@thebsh.namesys.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.