public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Jones <davej@redhat.com>
To: Andrew Morton <akpm@osdl.org>
Cc: Venkatesh Pallipadi <venkatesh.pallipadi@intel.com>,
	linux-kernel@vger.kernel.org, alexey.y.starikovskiy@intel.com
Subject: Re: [RFC] Adding queue_delayed_work_on interface for workqueues
Date: Fri, 30 Jun 2006 01:45:18 -0400	[thread overview]
Message-ID: <20060630054518.GF32729@redhat.com> (raw)
In-Reply-To: <20060628143242.486f9b15.akpm@osdl.org>

On Wed, Jun 28, 2006 at 02:32:42PM -0700, Andrew Morton wrote:

 > > +extern int FASTCALL(queue_delayed_work_on(int cpu, struct workqueue_struct *wq, struct work_struct *work, unsigned long delay));
 > 
 > Please wrap at 80-cols.

fixed up

 > I wouldn't bother making this FASTCALL.  It's an ugly thing, and why this
 > particular function?  And this isn't fastpath stuff.

fixed up

 > > -extern int schedule_delayed_work_on(int cpu, struct work_struct *work, unsigned long delay);
 > > +extern int FASTCALL(schedule_delayed_work_on(int cpu, struct work_struct *work, unsigned long delay));
 > 
 > Ditto.

ditto :)

 > >  }
 > >  
 > > +int fastcall queue_delayed_work_on(int cpu, struct workqueue_struct *wq,
 > > +			struct work_struct *work, unsigned long delay)
 > > +{
 > > +}
 > 
 > Feel free to add some kernel-doc for this function ;)

Venki, I'm lazy and it's past my bedtime, send a follow-up diff please ?

 > > @@ -608,6 +615,7 @@ void init_workqueues(void)
 > >  EXPORT_SYMBOL_GPL(__create_workqueue);
 > >  EXPORT_SYMBOL_GPL(queue_work);
 > >  EXPORT_SYMBOL_GPL(queue_delayed_work);
 > > +EXPORT_SYMBOL_GPL(queue_delayed_work_on);
 > >  EXPORT_SYMBOL_GPL(flush_workqueue);
 > >  EXPORT_SYMBOL_GPL(destroy_workqueue);
 > 
 > Opinions vary a bit, but I think we mostly prefer to put the
 > EXPORT_SYMBOL()s at the site of the thing which is being exported:
 >.. 
 > Then again, it's legit to follow existing local style too.  Someone will
 > come along later and fix it all in a single hit.  Whatever.

That someone was me. I did it as a follow-on for Venki's series.

All pushed out to cpufreq.git

		Dave

-- 
http://www.codemonkey.org.uk

      parent reply	other threads:[~2006-06-30  5:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-28 21:10 [RFC] Adding queue_delayed_work_on interface for workqueues Venkatesh Pallipadi
2006-06-28 21:32 ` Andrew Morton
2006-06-29 20:09   ` Dave Jones
2006-06-29 20:44     ` Andrew Morton
2006-06-30  5:45   ` Dave Jones [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=20060630054518.GF32729@redhat.com \
    --to=davej@redhat.com \
    --cc=akpm@osdl.org \
    --cc=alexey.y.starikovskiy@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=venkatesh.pallipadi@intel.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