From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Chris Paterson <Chris.Paterson2@renesas.com>
Cc: "stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: Re: Linux 4.19.89-rc1 5944fcdd errors
Date: Mon, 9 Dec 2019 18:36:37 +0100 [thread overview]
Message-ID: <20191209173637.GF1290729@kroah.com> (raw)
In-Reply-To: <TYAPR01MB228505DBC22568339F914C15B7580@TYAPR01MB2285.jpnprd01.prod.outlook.com>
On Mon, Dec 09, 2019 at 04:29:22PM +0000, Chris Paterson wrote:
> 3)
> Config: arm shmobile_defconfig
> Link: https://gitlab.com/cip-playground/linux-stable-rc-ci/-/jobs/373484089#L2249
> Probable culprit: 984d7a8bff57 ("pinctrl: sh-pfc: r8a7792: Fix VIN versioned groups")
> Issue log:
> 2249 drivers/pinctrl/sh-pfc/pfc-r8a7792.c:1750:38: error: macro "VIN_DATA_PIN_GROUP" passed 3 arguments, but takes just 2
> 2250 VIN_DATA_PIN_GROUP(vin1_data, 24, _b),
> 2251 ^
> 2252 drivers/pinctrl/sh-pfc/pfc-r8a7792.c:1750:2: error: 'VIN_DATA_PIN_GROUP' undeclared here (not in a function); did you mean 'PIN_MAP_TYPE_MUX_GROUP'?
> 2253 VIN_DATA_PIN_GROUP(vin1_data, 24, _b),
> 2254 ^~~~~~~~~~~~~~~~~~
> 2255 PIN_MAP_TYPE_MUX_GROUP
> 2256 drivers/pinctrl/sh-pfc/pfc-r8a7792.c:1751:38: error: macro "VIN_DATA_PIN_GROUP" passed 3 arguments, but takes just 2
> 2257 VIN_DATA_PIN_GROUP(vin1_data, 20, _b),
> 2258 ^
> 2259 drivers/pinctrl/sh-pfc/pfc-r8a7792.c:1753:38: error: macro "VIN_DATA_PIN_GROUP" passed 3 arguments, but takes just 2
> 2260 VIN_DATA_PIN_GROUP(vin1_data, 16, _b),
> 2261 ^
Now dropped for 4.19, 4.14, and 4.9 (2 patches for 4.19 here.)
thanks,
greg k-h
next prev parent reply other threads:[~2019-12-09 17:36 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-09 16:29 Linux 4.19.89-rc1 5944fcdd errors Chris Paterson
2019-12-09 16:34 ` Chris Paterson
2019-12-09 16:34 ` [cip-dev] " Chris Paterson
2019-12-09 16:53 ` Naresh Kamboju
2019-12-09 16:53 ` [cip-dev] " Naresh Kamboju
2019-12-09 17:02 ` Greg Kroah-Hartman
2019-12-09 17:04 ` Greg Kroah-Hartman
2019-12-09 17:36 ` Greg Kroah-Hartman [this message]
2019-12-09 21:56 ` Chris Paterson
2019-12-09 21:56 ` [cip-dev] " Chris Paterson
2019-12-10 7:35 ` Greg Kroah-Hartman
2019-12-10 7:35 ` [cip-dev] " Greg Kroah-Hartman
2019-12-10 14:42 ` Chris Paterson
2019-12-10 14:42 ` [cip-dev] " Chris Paterson
2019-12-10 14:55 ` Greg Kroah-Hartman
2019-12-10 14:55 ` [cip-dev] " Greg Kroah-Hartman
2019-12-10 15:20 ` Chris Paterson
2019-12-10 15:20 ` [cip-dev] " Chris Paterson
2019-12-10 20:59 ` Greg Kroah-Hartman
2019-12-10 20:59 ` [cip-dev] " Greg Kroah-Hartman
2019-12-11 10:52 ` Chris Paterson
2019-12-11 10:52 ` [cip-dev] " Chris Paterson
2019-12-11 12:19 ` Chen-Yu Tsai
2019-12-11 12:19 ` [cip-dev] " Chen-Yu Tsai
2019-12-11 13:45 ` Greg Kroah-Hartman
2019-12-11 13:45 ` [cip-dev] " Greg Kroah-Hartman
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=20191209173637.GF1290729@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=Chris.Paterson2@renesas.com \
--cc=stable@vger.kernel.org \
/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.