From: Arnd Bergmann <arnd@arndb.de>
To: Bartosz Golaszewski <brgl@bgdev.pl>
Cc: David Lechner <david@lechnology.com>,
Kevin Hilman <khilman@kernel.org>, Sekhar Nori <nsekhar@ti.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Bartosz Golaszewski <bgolaszewski@baylibre.com>,
Linux ARM <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v2 1/5] staging: media/davinci_vpfe: fix pinmux setup compilation
Date: Thu, 25 Jul 2019 16:45:05 +0200 [thread overview]
Message-ID: <CAK8P3a32tvPkYEiZMWxg+7weoAmZFPF31t2jw132f963ZeB_gQ@mail.gmail.com> (raw)
In-Reply-To: <20190725131257.6142-2-brgl@bgdev.pl>
On Thu, Jul 25, 2019 at 3:13 PM Bartosz Golaszewski <brgl@bgdev.pl> wrote:
>
> From: Arnd Bergmann <arnd@arndb.de>
>
> This fixes the following build error in davinci_vpfe.
>
> /git/arm-soc/drivers/staging/media/davinci_vpfe/dm365_isif.c: In function 'vpfe_isif_init':
> /git/arm-soc/drivers/staging/media/davinci_vpfe/dm365_isif.c:2031:2: error: implicit declaration of function 'davinci_cfg_reg'; did you mean 'omap_cfg_reg'? [-Werror=implicit-function-declaration]
> davinci_cfg_reg(DM365_VIN_CAM_WEN);
> ^~~~~~~~~~~~~~~
> omap_cfg_reg
> /git/arm-soc/drivers/staging/media/davinci_vpfe/dm365_isif.c:2031:18: error: 'DM365_VIN_CAM_WEN' undeclared (first use in this function); did you mean 'DM365_ISIF_MAX_CLDC'?
> davinci_cfg_reg(DM365_VIN_CAM_WEN);
> ^~~~~~~~~~~~~~~~~
>
> Signed-off-by: Arnd Bergmann <arnd@arndb.de>
> Signed-off-by: Bartosz Golaszewski <bgolaszewski@baylibre.com>
> ---
> drivers/staging/media/davinci_vpfe/Makefile | 5 -----
> drivers/staging/media/davinci_vpfe/dm365_isif.c | 8 +++-----
> drivers/staging/media/davinci_vpfe/dm365_isif.h | 2 --
> drivers/staging/media/davinci_vpfe/vpfe.h | 2 ++
> 4 files changed, 5 insertions(+), 12 deletions(-)
The driver has just been removed, so you can drop the patch now.
Arnd
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-07-25 14:45 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-25 13:12 [PATCH v2 0/5] ARM: make DaVinci part of the ARM v5 multiplatform build Bartosz Golaszewski
2019-07-25 13:12 ` [PATCH v2 1/5] staging: media/davinci_vpfe: fix pinmux setup compilation Bartosz Golaszewski
2019-07-25 14:45 ` Arnd Bergmann [this message]
2019-07-25 13:12 ` [PATCH v2 2/5] media: davinci-vpbe: remove obsolete includes Bartosz Golaszewski
2019-07-25 14:46 ` Arnd Bergmann
2019-07-25 13:12 ` [PATCH v2 3/5] davinci: fix sleep.S build error on ARMv4 Bartosz Golaszewski
2019-07-25 13:12 ` [PATCH v2 4/5] ARM: davinci: support multiplatform build for ARM v5 Bartosz Golaszewski
2019-09-09 7:38 ` Sekhar Nori
2019-09-09 19:38 ` Arnd Bergmann
2019-07-25 13:12 ` [PATCH v2 5/5] ARM: multi_v5_defconfig: make DaVinci part of the ARM v5 multiplatform build Bartosz Golaszewski
2019-09-09 7:38 ` Sekhar Nori
2019-07-25 14:57 ` [PATCH v2 0/5] ARM: " Arnd Bergmann
2019-08-05 8:31 ` Bartosz Golaszewski
2019-08-28 7:33 ` Bartosz Golaszewski
2019-08-28 7:44 ` Sekhar Nori
2019-08-28 7:55 ` Bartosz Golaszewski
2019-09-07 8:21 ` Arnd Bergmann
2019-09-08 13:31 ` Bartosz Golaszewski
2019-09-09 7:53 ` Sekhar Nori
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=CAK8P3a32tvPkYEiZMWxg+7weoAmZFPF31t2jw132f963ZeB_gQ@mail.gmail.com \
--to=arnd@arndb.de \
--cc=bgolaszewski@baylibre.com \
--cc=brgl@bgdev.pl \
--cc=david@lechnology.com \
--cc=khilman@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nsekhar@ti.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 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).