From: "Jan-Simon Möller" <dl9pf@gmx.de>
To: pageexec@freemail.hu
Cc: Daniel Vetter <daniel@ffwll.ch>,
Jani Nikula <jani.nikula@linux.intel.com>,
airlied@linux.ie, daniel.vetter@ffwll.ch,
intel-gfx@lists.freedesktop.org, linux-kernel@vger.kernel.org,
dri-devel@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH] [TRIVIAL] Fix declaration of intel_gmbus_{is_forced_bit/is_port_falid} in i915 driver.
Date: Mon, 06 May 2013 14:46:18 +0200 [thread overview]
Message-ID: <4246338.ENCyMUo2HP@aragorn.auenland.lan> (raw)
In-Reply-To: <5184CD16.8569.184037FF@pageexec.freemail.hu>
Ok, so let me resend a version with "static inline" .
Best,
JS
On Saturday 04 May 2013 10:55:50 PaX Team wrote:
> On 3 May 2013 at 15:03, Jani Nikula wrote:
> > >> This fixes a compilation issue with clang. An initial version of this
> > >> patch
> > >> was developed by PaX Team <pageexec at freemail.hu>.
> > >> This is respin of this patch.
> > >>
> > >> Signed-off-by: Jan-Simon Möller <dl9pf@gmx.de>
> > >> CC: pageexec@freemail.hu
> > >> CC: daniel.vetter@ffwll.ch
> > >> CC: airlied@linux.ie
> > >> CC: intel-gfx@lists.freedesktop.org
> > >> CC: dri-devel@lists.freedesktop.org
> > >> CC: linux-kernel@vger.kernel.org
> > >
> > > Picked up for -fixes, thanks for the patch.
> >
> > Please drop it.
> >
> > The patch removes the inline keyword, creating dozens of copies of the
>
> > functions, and consequently loads of warnings:
> in my original patch they were both static inline, not sure where the
> inline got lost...
--
Dipl.-Ing.
Jan-Simon Möller
jansimon.moeller@gmx.de
prev parent reply other threads:[~2013-05-06 12:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-03 9:17 dl9pf
2013-05-03 9:23 ` Daniel Vetter
2013-05-03 12:03 ` [Intel-gfx] " Jani Nikula
2013-05-03 16:16 ` Daniel Vetter
2013-05-04 8:55 ` PaX Team
2013-05-06 12:46 ` Jan-Simon Möller [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=4246338.ENCyMUo2HP@aragorn.auenland.lan \
--to=dl9pf@gmx.de \
--cc=airlied@linux.ie \
--cc=daniel.vetter@ffwll.ch \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pageexec@freemail.hu \
/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
all inboxes | Powered by JetHome®