mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "shiva g" <shiva@isofttech.com>
To: "Sam Ravnborg" <sam@ravnborg.org>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: mark_bh in Linux 2.6.12 kernel
Date: Wed, 29 Mar 2006 16:31:49 +0530	[thread overview]
Message-ID: <011d01c65320$2d5c2430$7b01a8c0@shiva> (raw)
In-Reply-To: <20060329105600.GA13383@mars.ravnborg.org>

Here is the source

static __inline__ void usbd_schedule_device_bh(struct usb_device_instance 
*device)
{
    if (device && (device->status != USBD_CLOSING) && 
!device->device_bh.sync) {
        queue_task(&device->device_bh, &tq_immediate);
        mark_bh(IMMEDIATE_BH);
    }
}

Also,in the below code, will replacing "schedule_task" simply by 
"schedule_work" work?
static __inline__ void usbd_schedule_function_bh(struct usb_device_instance 
*device)
{
    if (device && (device->status != USBD_CLOSING) && 
!device->function_bh.sync) {
    schedule_task(&device->function_bh);
    }

---- Original Message ----- 
From: "Sam Ravnborg" <sam@ravnborg.org>
To: "shiva g" <shiva@isofttech.com>
Cc: <linux-kernel@vger.kernel.org>
Sent: Wednesday, March 29, 2006 4:26 PM
Subject: Re: mark_bh in Linux 2.6.12 kernel


> On Wed, Mar 29, 2006 at 04:12:43PM +0530, shiva g wrote:
>> Hi all,
>>    We are porting a usb host controller driver from 2.4.18 kernel to 
>> 2.6.12
>> kernel. We face some issues with
>> mark_bh( ) call. Can anyone suggest us how we proceed in porting 
>> mark_bh( )
>> in the 2.6.12 kernel.
> Posting the source may give you more/better feedback...
>
> Sam
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/ 


  reply	other threads:[~2006-03-29 11:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-29 10:42 shiva g
2006-03-29 10:56 ` Sam Ravnborg
2006-03-29 11:01   ` shiva g [this message]
2006-03-29 13:00     ` Peter Hagervall

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='011d01c65320$2d5c2430$7b01a8c0@shiva' \
    --to=shiva@isofttech.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sam@ravnborg.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

all inboxes | Powered by JetHome®