From: Tomi Valkeinen <tomi.valkeinen@ti.com>
To: David Airlie <airlied@redhat.com>
Cc: "Vincent Stehlé" <vincent.stehle@freescale.com>,
linux-next@vger.kernel.org, linux-fbdev@vger.kernel.org,
"Jean-Christophe Plagniol-Villard" <plagnioj@jcrosoft.com>,
trivial@kernel.org
Subject: Re: [PATCH linux-next] fb: make fp_get_options name argument const
Date: Thu, 27 Jun 2013 06:31:04 +0000 [thread overview]
Message-ID: <51CBDC28.9080808@ti.com> (raw)
In-Reply-To: <1927037966.2377585.1372310085417.JavaMail.root@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1097 bytes --]
On 27/06/13 08:14, David Airlie wrote:
>>>
>>>
>>> Hi,
>>>
>>> I remarked this warning while building linux-next with imx_v6_v7_defconfig.
>>> Is changing fb_get_options prototype "permitted", please?
>>
>> I don't see how changing the parameter to const could break anything, so
>> I've applied this to fbdev-3.11 branch.
>>
>
> Hi Tomi,
>
> What tree does Jean-Christophe PLAGNIOL-VILLARD control?
git://git.kernel.org/pub/scm/linux/kernel/git/plagnioj/linux-fbdev.git
> he said he merged the original patch to fix this from Ville, but I've no idea
> where it ended up, so I just didn't merge it to drm-next at the time.
>
> Message-Id: <1370619787-15341-3-git-send-email-ville.syrjala@linux.intel.com>
>
> is the original properly attributed fix.
Hmm, ok. He asked me to collect fbdev patches as he's been away, so I
went through my inbox and picked up what's there. I can't see the patch
from Ville in Jean-Christophe's tree.
Jean-Christophe, have you taken that (and maybe other patches) but you
haven't pushed them to the kernel.org tree?
Tomi
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 901 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Tomi Valkeinen <tomi.valkeinen@ti.com>
To: David Airlie <airlied@redhat.com>
Cc: "Vincent Stehlé" <vincent.stehle@freescale.com>,
linux-next@vger.kernel.org, linux-fbdev@vger.kernel.org,
"Jean-Christophe Plagniol-Villard" <plagnioj@jcrosoft.com>,
trivial@kernel.org
Subject: Re: [PATCH linux-next] fb: make fp_get_options name argument const
Date: Thu, 27 Jun 2013 09:31:04 +0300 [thread overview]
Message-ID: <51CBDC28.9080808@ti.com> (raw)
In-Reply-To: <1927037966.2377585.1372310085417.JavaMail.root@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1097 bytes --]
On 27/06/13 08:14, David Airlie wrote:
>>>
>>>
>>> Hi,
>>>
>>> I remarked this warning while building linux-next with imx_v6_v7_defconfig.
>>> Is changing fb_get_options prototype "permitted", please?
>>
>> I don't see how changing the parameter to const could break anything, so
>> I've applied this to fbdev-3.11 branch.
>>
>
> Hi Tomi,
>
> What tree does Jean-Christophe PLAGNIOL-VILLARD control?
git://git.kernel.org/pub/scm/linux/kernel/git/plagnioj/linux-fbdev.git
> he said he merged the original patch to fix this from Ville, but I've no idea
> where it ended up, so I just didn't merge it to drm-next at the time.
>
> Message-Id: <1370619787-15341-3-git-send-email-ville.syrjala@linux.intel.com>
>
> is the original properly attributed fix.
Hmm, ok. He asked me to collect fbdev patches as he's been away, so I
went through my inbox and picked up what's there. I can't see the patch
from Ville in Jean-Christophe's tree.
Jean-Christophe, have you taken that (and maybe other patches) but you
haven't pushed them to the kernel.org tree?
Tomi
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 901 bytes --]
next prev parent reply other threads:[~2013-06-27 6:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-18 14:23 [PATCH linux-next] fb: make fp_get_options name argument const Vincent Stehlé
2013-06-18 14:23 ` Vincent Stehlé
2013-06-26 13:21 ` Tomi Valkeinen
2013-06-26 13:21 ` Tomi Valkeinen
2013-06-27 5:14 ` David Airlie
2013-06-27 5:14 ` David Airlie
2013-06-27 6:31 ` Tomi Valkeinen [this message]
2013-06-27 6:31 ` Tomi Valkeinen
2013-06-27 8:51 ` Jean-Christophe PLAGNIOL-VILLARD
2013-06-27 8:51 ` Jean-Christophe PLAGNIOL-VILLARD
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=51CBDC28.9080808@ti.com \
--to=tomi.valkeinen@ti.com \
--cc=airlied@redhat.com \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=plagnioj@jcrosoft.com \
--cc=trivial@kernel.org \
--cc=vincent.stehle@freescale.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 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.