From: "Leon Woestenberg" <leon.woestenberg@gmail.com>
To: "Steven Rostedt" <rostedt@goodmis.org>
Cc: RT <linux-rt-users@vger.kernel.org>
Subject: Re: [PATCH -rt] Add schedule_work_prio() and queue_work_prio().
Date: Mon, 30 Jun 2008 18:38:21 +0200 [thread overview]
Message-ID: <c384c5ea0806300938ucf1cbc2j39380ee33eb8bf12@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0806300846590.13037@gandalf.stny.rr.com>
Steven,
On Mon, Jun 30, 2008 at 2:47 PM, Steven Rostedt <rostedt@goodmis.org> wrote:
> On Sat, 28 Jun 2008, Leon Woestenberg wrote:
>> Against 2.6.25.8-rt7, only compile tested.
>>
>> +int queue_work_prio(struct workqueue_struct *wq, struct work_struct
>> *work, int prio)
>> {
>> int ret = 0, cpu = raw_smp_processor_id();
>>
>> @@ -184,6 +185,25 @@
>> }
>> return ret;
>> }
>> +EXPORT_SYMBOL_GPL(queue_work_prio);
>
> This function doesn't look like it does anything with the new "prio"
> field.
>
I have submitted a newer patch in a seperate email that fixes this.
Regards,
--
Leon
prev parent reply other threads:[~2008-06-30 16:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-28 17:23 [PATCH -rt] Add schedule_work_prio() and queue_work_prio() Leon Woestenberg
2008-06-30 9:18 ` Leon Woestenberg
2008-06-30 12:47 ` Steven Rostedt
2008-06-30 16:38 ` Leon Woestenberg [this message]
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=c384c5ea0806300938ucf1cbc2j39380ee33eb8bf12@mail.gmail.com \
--to=leon.woestenberg@gmail.com \
--cc=linux-rt-users@vger.kernel.org \
--cc=rostedt@goodmis.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).