From: Grant Likely <grant.likely@secretlab.ca>
To: Timur Tabi <timur@freescale.com>
Cc: linuxppc-dev@ozlabs.org, smaclennan@pikatech.com,
scottwood@freescale.com
Subject: Re: [PATCH v7] introduce macro spin_event_timeout()
Date: Thu, 14 May 2009 10:10:57 -0600 [thread overview]
Message-ID: <fa686aa40905140910i194acbd7y34142720874b8299@mail.gmail.com> (raw)
In-Reply-To: <4A0C40D4.1090508@freescale.com>
On Thu, May 14, 2009 at 10:03 AM, Timur Tabi <timur@freescale.com> wrote:
> Grant Likely wrote:
>
>> This version looks good to me. =A0Who's the first user? (I'd like to see
>> that something is ready to use this before merging it)
>
> I was going to do it the other way around - wait until this patch is merg=
ed, and then update some code to use it. =A0After all, it's easier to use a=
macro if it already exists in a header file. :-)
Heh, I think you miss my meaning. Of course this patch must be merged
before any users. I just want to hold off merging it until I see
viable patches on the mailing list which depend on it.
In other words, write your patches which use it and submit the lot as
a patch series with this patch as the first. That gives some evidence
that this macro will actually be used and useful.
g.
--=20
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.
next prev parent reply other threads:[~2009-05-14 16:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-05 21:53 [PATCH v7] introduce macro spin_event_timeout() Timur Tabi
2009-05-06 0:43 ` Sean MacLennan
2009-05-14 15:13 ` Grant Likely
2009-05-14 16:03 ` Timur Tabi
2009-05-14 16:10 ` Grant Likely [this message]
2009-05-18 22:49 ` Timur Tabi
2009-05-19 2:58 ` Grant Likely
2009-05-19 3:57 ` Sean MacLennan
2009-05-19 12:30 ` Grant Likely
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=fa686aa40905140910i194acbd7y34142720874b8299@mail.gmail.com \
--to=grant.likely@secretlab.ca \
--cc=linuxppc-dev@ozlabs.org \
--cc=scottwood@freescale.com \
--cc=smaclennan@pikatech.com \
--cc=timur@freescale.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 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).