From: Sean Young <sean@mess.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Mauro Carvalho Chehab <mchehab@kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: build failure after merge of the v4l-dvb-next tree
Date: Mon, 20 Sep 2021 08:39:48 +0100 [thread overview]
Message-ID: <20210920073948.GA8800@gofer.mess.org> (raw)
In-Reply-To: <20210920101948.34a93713@canb.auug.org.au>
Hi Mauro,
On Mon, Sep 20, 2021 at 10:19:48AM +1000, Stephen Rothwell wrote:
> Hi all,
>
> After merging the v4l-dvb-next tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
>
> drivers/media/rc/ir_toy.c: In function 'irtoy_tx':
> drivers/media/rc/ir_toy.c:332:36: error: 'STATE_RESET' undeclared (first use in this function)
> 332 | sizeof(COMMAND_SMODE_EXIT), STATE_RESET);
> | ^~~~~~~~~~~
> drivers/media/rc/ir_toy.c:332:36: note: each undeclared identifier is reported only once for each function it appears in
>
> Caused by commit
>
> 6a014f20734d ("media: ir_toy: allow tx carrier to be set")
This commit renames STATE_RESET to STATE_COMMAND_NO_RESP.
> interacting with commit
>
> f0c15b360fb6 ("media: ir_toy: prevent device from hanging during transmit")
This commit uses STATE_RESET.
> from the v4l-vdb-fixes tree.
>
> I have applied the following merge fix patch for today.
I'm not sure what the best solution is here. Once commit f0c15b360fb6 makes
it into Linus' tree and then is merged back into mediastage, commit
6a014f20734d can be rebased.
Thanks
Sean
>
> From: Stephen Rothwell <sfr@canb.auug.org.au>
> Date: Mon, 20 Sep 2021 10:14:37 +1000
> Subject: [PATCH] fix for "media: ir_toy: allow tx carrier to be set"
>
> Signed-off-by: Stephen Rothwell <sfr@canb.auug.org.au>
> ---
> drivers/media/rc/ir_toy.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/media/rc/ir_toy.c b/drivers/media/rc/ir_toy.c
> index 9ea91d418635..71aced52248f 100644
> --- a/drivers/media/rc/ir_toy.c
> +++ b/drivers/media/rc/ir_toy.c
> @@ -329,7 +329,7 @@ static int irtoy_tx(struct rc_dev *rc, uint *txbuf, uint count)
> // with its led on. It does not respond to any command when this
> // happens. To work around this, re-enter sample mode.
> err = irtoy_command(irtoy, COMMAND_SMODE_EXIT,
> - sizeof(COMMAND_SMODE_EXIT), STATE_RESET);
> + sizeof(COMMAND_SMODE_EXIT), STATE_COMMAND_NO_RESP);
> if (err) {
> dev_err(irtoy->dev, "exit sample mode: %d\n", err);
> return err;
> --
> 2.32.0
>
> --
> Cheers,
> Stephen Rothwell
next prev parent reply other threads:[~2021-09-20 7:39 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-20 0:19 linux-next: build failure after merge of the v4l-dvb-next tree Stephen Rothwell
2021-09-20 7:39 ` Sean Young [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-05-06 0:49 Stephen Rothwell
2024-05-07 11:56 ` Sakari Ailus
2024-05-01 0:22 Stephen Rothwell
2023-10-09 0:08 Stephen Rothwell
2023-10-09 9:25 ` Bryan O'Donoghue
2023-10-09 9:50 ` Hans Verkuil
2021-05-19 23:55 Stephen Rothwell
2020-06-03 2:46 Stephen Rothwell
2020-06-03 8:13 ` Mauro Carvalho Chehab
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=20210920073948.GA8800@gofer.mess.org \
--to=sean@mess.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mchehab@kernel.org \
--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).