linux-kernel - Re: [PATCH] staging, gma500: Fix warning in power.c

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CADZ9YHiW=RcS2bJd3hgNk+kwtQu5=8wgYM1rqv1EO9pbad7aBA@mail.gmail.com>
Date:	Thu, 29 Dec 2011 11:42:59 +0600
From:	Rakib Mullick <rakib.mullick@...il.com>
To:	Alan Cox <alan@...ux.intel.com>
Cc:	linux-kernel@...r.kernel.org, Greg Kroah-Hartman <gregkh@...e.de>,
	akpm@...ux-foundation.org
Subject: Re: [PATCH] staging, gma500: Fix warning in power.c

On Thu, Dec 29, 2011 at 11:31 AM, Rakib Mullick <rakib.mullick@...il.com> wrote:
> On Wed, Dec 28, 2011 at 8:04 PM, Alan Cox <alan@...ux.intel.com> wrote:
>> On Fri, 23 Dec 2011 00:46:45 +0600
>> Rakib Mullick <rakib.mullick@...il.com> wrote:
>>
>>>  gma_resume_display() wants 'struct pci_dev *' as it's parameter, so
>>> lets pass dev->pdev instead of dev. Fixes the following warning.
>>>
>>> drivers/staging/gma500/power.c: In function ‘gma_power_begin’:
>>> drivers/staging/gma500/power.c:269:3: warning: passing argument 1 of
>>> ‘gma_resume_display’ from incompatible pointer type
>>> drivers/staging/gma500/power.c:99:13: note: expected ‘struct pci_dev
>>> *’ but argument is of type ‘struct drm_device *’
>>
>> This staging driver is now dead and replaced with
>> drivers/gpu/drm/gma500/. Thanks for the fix however
>>
> The patch was prepared against 3.2-rc6 and at the time of preparing
> the patch that was the latest rc release.
>
Do I have to resend the patch, prepared against -rc7? Patch is on it's
way towards mainline through linux-next (Greg took it in his tree
previously). It might conflict during merging, not sure. If requires I
can send it again.

Thanks,
Rakib
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/