linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Hauke Mehrtens <hauke@hauke-m.de>
Cc: mcgrof@gmail.com, lf_driver_backport@lists.linux-foundation.org,
	linux-wireless@vger.kernel.org
Subject: Re: [RFC 0/9] compat-wireless: restructure header files in compat
Date: Thu, 03 May 2012 20:58:10 +0200	[thread overview]
Message-ID: <1336071490.5167.7.camel@jlt3.sipsolutions.net> (raw)
In-Reply-To: <1335463674-13003-1-git-send-email-hauke@hauke-m.de> (sfid-20120426_200811_897687_43DE405B)

On Thu, 2012-04-26 at 20:07 +0200, Hauke Mehrtens wrote:
> The patch series moves the compat code from include/linux/compat-*.h 
> into new files with the same name as the file where this code is placed 
> in the mainline kernel. With this approach we do not have to include 
> all include/linux/compat-*.h files in the build process any more, but 
> we extend the existing header files by the code needed.
> 
> This compiles without any warnings for me with kernel 3.2 to 3.4 and 
> fixes the problems with pr_fmt() without the need of any patch.
> Sometimes I had problems compiling compat-wireless, because some header 
> file I would not like to include was included because of compat-2.6.h 
> included mostly every header file available in the kernel.
> 
> This patch series is only done to support kernel >= 3.2, supporting the 
> other versions is just more work, but I want to have some responses on 
> this first. There are probably some other problems and some more 
> cleanup is possible.
> In the end we will remove the include/linux/compat-*.h files.
> 
> I have a problem where compat does changes to header files provided by 
> compat-wireless like #define NL80211_FEATURE_SK_TX_STATUS 0 in compat-
> 2.6.33.h. To make this work we should add an other include directory in 
> compat-wireless.
> The hierarchy of include directories should be this: 1. include dir 
> from compat, 2. include dir from compat-wireless, 3. the kernel include 
> dir, now the 1. and the 2. are but into one directory.


I think this is worthwhile. There may be some issues with it,
particularly when header files are renamed, but I think those can be
solved relatively easily, like we already did with tracing.

johannes


      parent reply	other threads:[~2012-05-03 18:58 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-26 18:07 [RFC 0/9] compat-wireless: restructure header files in compat Hauke Mehrtens
2012-04-26 18:07 ` [RFC c 1/9] compat: move compat_system_workqueue_{create,destroy} and compat_pm_qos_power_{init,deinit} Hauke Mehrtens
2012-04-26 18:07 ` [RFC c-w 1/4] compat-wireless: fix header of compat-autoconf.h Hauke Mehrtens
2012-04-26 18:07 ` [RFC c 2/9] compat: include compat_autoconf.h Hauke Mehrtens
2012-04-26 18:07 ` [RFC c-w 2/4] compat-wireless: also copy include/generated/ from compat Hauke Mehrtens
2012-05-03 18:57   ` Johannes Berg
2012-05-03 19:05     ` Hauke Mehrtens
2012-05-03 19:20       ` Johannes Berg
2012-04-26 18:07 ` [RFC c 3/9] compat: move br_port_exists Hauke Mehrtens
2012-04-26 18:07 ` [RFC c-w 3/4] compat-wireless: do not include linux/compat-2.6.h any more Hauke Mehrtens
2012-04-26 18:07 ` [RFC c 4/9] compat: move netdev_attach_ops Hauke Mehrtens
2012-04-26 18:07 ` [RFC c-w 4/4] compat-wireless: copy *.h files from compat/compat Hauke Mehrtens
2012-04-26 18:07 ` [RFC c 5/9] compat: move compat_pci_{suspend,resume} Hauke Mehrtens
2012-04-26 18:07 ` [RFC c 6/9] compat: move simple_open() Hauke Mehrtens
2012-04-26 18:07 ` [RFC c 7/9] compat: move code from compat-3.4.h Hauke Mehrtens
2012-04-26 18:07 ` [RFC c 8/9] compat: move code from compat-3.3.h Hauke Mehrtens
2012-04-26 18:07 ` [RFC c 9/9] compat: do not include compat-2.6.h Hauke Mehrtens
2012-05-03 18:58 ` Johannes Berg [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=1336071490.5167.7.camel@jlt3.sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=hauke@hauke-m.de \
    --cc=lf_driver_backport@lists.linux-foundation.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=mcgrof@gmail.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;
as well as URLs for NNTP newsgroup(s).