From: Nigel Cunningham <ncunningham@users.sourceforge.net>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Is this too ugly to merge?
Date: Fri, 09 Jan 2004 17:50:14 +1300 [thread overview]
Message-ID: <1073623814.10388.6.camel@laptop-linux> (raw)
In-Reply-To: <3FFE31B6.1030205@osdl.org>
[-- Attachment #1: Type: text/plain, Size: 976 bytes --]
Well, they manipulate a variable local to the procedure, so I believe
so. I have to record which routine the activity flag was set it,
possibly pass through other routines that could set it and not clear it
until we get back to the routine where it was first set. I'm sure
there'd be another way, but I can only think of more complicated ones,
not simpler and prettier :>
Nigel
On Fri, 2004-01-09 at 17:44, Stephen Hemminger wrote:
> Nigel Cunningham wrote:
>
> > Hi all.
> >
> > I'm wanting to the opinion, if I may, of more experienced people
> > regarding changes I have implemented in my version of Software Suspend,
> > which I want to merge with Patrick and Pavel. Since I'm don't expect
> > that you're all familiar with how my version works, I'll give a fair bit
> > of background before I come to the question.
>
> Do they all have to be big ugly macros?
>
--
My work on Software Suspend is graciously brought to you by
LinuxFund.org.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-01-09 4:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-09 0:58 Is this too ugly to merge? Nigel Cunningham
2004-01-09 4:44 ` Stephen Hemminger
2004-01-09 4:50 ` Nigel Cunningham [this message]
2004-01-09 5:35 ` Nigel Cunningham
2004-01-13 10:45 ` Pavel Machek
2004-01-13 11:49 ` Pavel Machek
2004-01-19 0:44 ` Nigel Cunningham
2004-01-19 9:51 ` Pavel Machek
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=1073623814.10388.6.camel@laptop-linux \
--to=ncunningham@users.sourceforge.net \
--cc=linux-kernel@vger.kernel.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