From: "Luis R. Rodriguez" <rodrigue@qca.qualcomm.com>
To: Arik Nemtsov <arik@wizery.com>
Cc: Hauke Mehrtens <hauke@hauke-m.de>,
<linux-wireless@vger.kernel.org>, <mcgrof@kernel.org>,
"backports@vger.kernel.org" <backports@vger.kernel.org>
Subject: Re: [PATCH] backports: rename some mem functions to not break custom kernels
Date: Tue, 13 Aug 2013 14:11:08 -0700 [thread overview]
Message-ID: <20130813211108.GM17130@pogo> (raw)
In-Reply-To: <CA+XVXfe65N5+iXQ6-5fST=PDKk4Hk0sRk04UH+oXoDpc1DTVyw@mail.gmail.com>
On Tue, Aug 13, 2013 at 05:47:53PM +0300, Arik Nemtsov wrote:
> On Mon, Aug 12, 2013 at 7:24 PM, Hauke Mehrtens <hauke@hauke-m.de> wrote:
> > adding the LINUX_BACKPORT() line should be enough to rename it
> > everywhere in backprots, so you do not have to modify
> > backport/compat/backport-3.11.c or manually add the prefix anywhere else.
> >
> > Could you try if this fixes your problems with phys_wc_to_mtrr_index:
> >
> > ...
> > +#define phys_wc_to_mtrr_index LINUX_BACKPORT(phys_wc_to_mtrr_index)
> > #ifdef CONFIG_MTRR
> > extern int phys_wc_to_mtrr_index(int handle);
> > #else
> > static inline int phys_wc_to_mtrr_index(int handle)
> > {
> > return -1;
> > }
> > #endif /* CONFIG_MTRR */
> >
>
> Thanks. It seems to do the trick. The attached patch solves the issue.
> Luis - any comments on this one?
I welcome a new patch in proper form with a Signed-off-by by the author.
Luis
next prev parent reply other threads:[~2013-08-13 21:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-07 8:52 [PATCH] backports: rename some mem functions to not break custom kernels Arik Nemtsov
2013-08-07 23:00 ` Hauke Mehrtens
2013-08-08 6:45 ` Arik Nemtsov
2013-08-12 16:24 ` Hauke Mehrtens
2013-08-13 14:47 ` Arik Nemtsov
2013-08-13 21:11 ` Luis R. Rodriguez [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-08-14 7:48 Arik Nemtsov
2013-08-16 3:14 ` Luis R. Rodriguez
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=20130813211108.GM17130@pogo \
--to=rodrigue@qca.qualcomm.com \
--cc=arik@wizery.com \
--cc=backports@vger.kernel.org \
--cc=hauke@hauke-m.de \
--cc=linux-wireless@vger.kernel.org \
--cc=mcgrof@kernel.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