From: Zefir Kurtisi <zefir.kurtisi@neratec.com>
To: Andy Gospodarek <andy@greyhouse.net>
Cc: Phil Perry <phil@elrepo.org>,
mcgrof@frijolero.org,
lf driver backport
<lf_driver_backport@lists.linux-foundation.org>,
linux-wireless@vger.kernel.org
Subject: Re: [PATCH v2] compat: support RHEL6.3 as a build target
Date: Thu, 9 Aug 2012 15:26:04 +0200 (CEST) [thread overview]
Message-ID: <2121451356.93690.1344518764022.JavaMail.root@neratec.com> (raw)
In-Reply-To: <1344487215-24143-1-git-send-email-andy@greyhouse.net>
On 08/09/2012 06:40 AM, Andy Gospodarek wrote:
> This patch allows me to compile and load the latest compat modules on
> RHEL6.3. Users of compat on RHEL6 should note that you should set
> CONFIG_COMPAT_KFIFO=n as those bits are not needed at all.
>
> [...]
>
> diff --git a/include/linux/compat-2.6.36.h b/include/linux/compat-2.6.36.h
> index 56d5961..09e4b6f 100644
> --- a/include/linux/compat-2.6.36.h
> +++ b/include/linux/compat-2.6.36.h
> @@ -98,6 +98,8 @@ struct pm_qos_request_list {
> * Dummy printk for disabled debugging statements to use whilst maintaining
> * gcc's format and side-effect checking.
> */
> +/* mask no_printk as RHEL6 backports this */
> +#define no_printk(...) compat_no_printk(...)
> static inline __attribute__ ((format (printf, 1, 2)))
> int no_printk(const char *s, ...) { return 0; }
>
> [...]
This at least breaks compilation on 2.6.35-22 with gcc throwing a
compat-2.6.36.h:104: error: ISO C requires a named argument before ‘...’
It looks like no_printk() needs to be renamed to compat_no_printk()
to make it work as intended.
This is a systematic mistake at several sections of this patch, where
the original function needs to be prefixed by 'compat_' to match the
related macro.
---
diff --git a/include/linux/compat-2.6.36.h b/include/linux/compat-2.6.36.h
index 8b02260..b6757c3 100644
--- a/include/linux/compat-2.6.36.h
+++ b/include/linux/compat-2.6.36.h
@@ -101,7 +101,7 @@ struct pm_qos_request_list {
/* mask no_printk as RHEL6 backports this */
#define no_printk(...) compat_no_printk(...)
static inline __attribute__ ((format (printf, 1, 2)))
-int no_printk(const char *s, ...) { return 0; }
+int compat_no_printk(const char *s, ...) { return 0; }
#ifndef alloc_workqueue
#define alloc_workqueue(name, flags, max_active) __create_workqueue(name, flags, max_active, 0)
next prev parent reply other threads:[~2012-08-09 13:26 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-09 4:40 [PATCH v2] compat: support RHEL6.3 as a build target Andy Gospodarek
2012-08-09 4:45 ` Luis R. Rodriguez
2012-08-09 13:26 ` Zefir Kurtisi [this message]
2012-08-10 1:27 ` Luis R. Rodriguez
2012-08-10 2:27 ` Andy Gospodarek
2012-08-10 3:13 ` [Lf_driver_backport] " Andy Gospodarek
2012-08-10 6:05 ` Luis R. Rodriguez
[not found] ` <CAHashqCmcgXXDyyqwEYefTMXFDVFKm9GKydfbS14UCY_L443Vg@mail.gmail.com>
2012-08-09 22:14 ` Phil Perry
2012-08-10 8:50 ` Zefir Kurtisi
2012-08-10 17:18 ` Hauke Mehrtens
2012-08-10 18:28 ` Andy Gospodarek
2012-08-10 19:50 ` Luis R. Rodriguez
2012-08-10 19:51 ` Andy Gospodarek
2012-08-10 23:48 ` Hauke Mehrtens
2012-08-10 17:19 ` 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=2121451356.93690.1344518764022.JavaMail.root@neratec.com \
--to=zefir.kurtisi@neratec.com \
--cc=andy@greyhouse.net \
--cc=lf_driver_backport@lists.linux-foundation.org \
--cc=linux-wireless@vger.kernel.org \
--cc=mcgrof@frijolero.org \
--cc=phil@elrepo.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;
as well as URLs for NNTP newsgroup(s).