public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: linux-kernel@vger.kernel.org, alan@lxorguk.ukuu.org.uk,
	sailer@ife.ee.ethz.ch, bhards@bigpond.net.au,
	torvalds@transmeta.com
Subject: Re: [PATCH] USB set-bit takes a long tweaks
Date: Tue, 16 Apr 2002 08:53:35 -0700	[thread overview]
Message-ID: <20020416155334.GD27287@kroah.com> (raw)
In-Reply-To: <E16xP4X-0005OC-00@wagner.rustcorp.com.au>

On Tue, Apr 16, 2002 at 07:16:01PM +1000, Rusty Russell wrote:
> This removes gratuitous & operators in front of USB's
> dev->bus->devmap.devicemap and state->unitbitmap, for bitops.
> 
> This just makes it so it doesn't warn when set_bit et. al take a
> long...
> 
> No object code changes,

Thanks, I've applied this to my trees, and will include it in the next
round of changesets to Linus.


greg k-h

      reply	other threads:[~2002-04-16 16:54 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-16  9:16 [PATCH] USB set-bit takes a long tweaks Rusty Russell
2002-04-16 15:53 ` Greg KH [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=20020416155334.GD27287@kroah.com \
    --to=greg@kroah.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=bhards@bigpond.net.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rusty@rustcorp.com.au \
    --cc=sailer@ife.ee.ethz.ch \
    --cc=torvalds@transmeta.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