All of lore.kernel.org
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Hauke Mehrtens <hauke@hauke-m.de>
Cc: Stefan Assmann <sassmann@kpanic.de>,
	mcgrof@kernel.org, backports@vger.kernel.org
Subject: Re: [PATCH] backports: remove obsolete linux/bitops.h header
Date: Wed, 20 Nov 2013 09:20:17 +0100	[thread overview]
Message-ID: <1384935617.14295.1.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <528BEB63.3080600@hauke-m.de> (sfid-20131119_235133_050957_98574914)

On Tue, 2013-11-19 at 23:51 +0100, Hauke Mehrtens wrote:
> On 11/18/2013 03:26 PM, Stefan Assmann wrote:
> > The header seems to be obsolete. Removing it and running devel/ckmake didn't
> > reveal any errors. Missing parts can always be re-added in the new
> > include_next fashion if necessary.
> > 
> > Signed-off-by: Stefan Assmann <sassmann@kpanic.de>
> 
> Some of these functions are needed, because they are not provided by old
> kernel versions.

Overall the idea seems right though - we should have something like

#ifndef __BACKPORT_BITOPS_H
#define __BACKPORT_BITOPS_H
#include_next <linux/bitops.h>

#ifndef for_each_set_bit
#define for_each_set_bit(...) \
	...
#endif

#if kernel_version < 2.6.38
static inline __s32 sign_extend32(...) { ... }
#endif

etc.

#endif /* __BACKPORT_BITOPS_H */

I think.

johannes


  reply	other threads:[~2013-11-20  8:20 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-18 14:26 [PATCH] backports: remove obsolete linux/bitops.h header Stefan Assmann
2013-11-19 22:51 ` Hauke Mehrtens
2013-11-20  8:20   ` Johannes Berg [this message]
2013-11-20  8:29   ` Stefan Assmann
2013-11-20  8:36     ` Johannes Berg
2013-11-20 11:26       ` Stefan Assmann
2013-11-20 11:36         ` Hauke Mehrtens

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=1384935617.14295.1.camel@jlt4.sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=backports@vger.kernel.org \
    --cc=hauke@hauke-m.de \
    --cc=mcgrof@kernel.org \
    --cc=sassmann@kpanic.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.