From: Randy Dunlap <rdunlap@infradead.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-media <linux-media@vger.kernel.org>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Sakari Ailus <sakari.ailus@linux.intel.com>
Subject: Re: linux-next: Tree for Oct 12 (drivers/staging/media/atomisp/)
Date: Mon, 12 Oct 2020 08:33:53 -0700 [thread overview]
Message-ID: <e9339988-4ff0-ddf6-9a52-09863ca66963@infradead.org> (raw)
In-Reply-To: <20201012205906.51237c67@canb.auug.org.au>
On 10/12/20 2:59 AM, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20201009:
>
on x86_64:
In file included from ../drivers/staging/media/atomisp//pci/ia_css_control.h:25:0,
from ../drivers/staging/media/atomisp//pci/ia_css.h:28,
from ../drivers/staging/media/atomisp//pci/atomisp_compat_css20.h:24,
from ../drivers/staging/media/atomisp//pci/atomisp_compat.h:22,
from ../drivers/staging/media/atomisp/pci/mmu/sh_mmu_mrfld.c:23:
../drivers/staging/media/atomisp//pci/ia_css_firmware.h:52:29: warning: ‘struct device’ declared inside parameter list will not be visible outside of this definition or declaration
ia_css_load_firmware(struct device *dev, const struct ia_css_env *env,
^~~~~~
In file included from ../drivers/staging/media/atomisp//pci/ia_css.h:28:0,
from ../drivers/staging/media/atomisp//pci/atomisp_compat_css20.h:24,
from ../drivers/staging/media/atomisp//pci/atomisp_compat.h:22,
from ../drivers/staging/media/atomisp/pci/mmu/sh_mmu_mrfld.c:23:
../drivers/staging/media/atomisp//pci/ia_css_control.h:49:24: warning: ‘struct device’ declared inside parameter list will not be visible outside of this definition or declaration
int ia_css_init(struct device *dev,
^~~~~~
--
~Randy
Reported-by: Randy Dunlap <rdunlap@infradead.org>
prev parent reply other threads:[~2020-10-12 15:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-12 9:59 linux-next: Tree for Oct 12 Stephen Rothwell
2020-10-12 15:33 ` Randy Dunlap [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=e9339988-4ff0-ddf6-9a52-09863ca66963@infradead.org \
--to=rdunlap@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=sakari.ailus@linux.intel.com \
--cc=sfr@canb.auug.org.au \
/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).