From: "Gustavo A. R. Silva" <gustavo@embeddedor.com>
To: Sasha Levin <sashal@kernel.org>, Ian Abbott <abbotti@mev.co.uk>
Cc: devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org
Subject: Re: [PATCH] staging: comedi: ni_660x: fix missing break in switch statement
Date: Mon, 18 Feb 2019 15:19:23 -0600 [thread overview]
Message-ID: <8b7905e6-6e77-d473-fb6a-55e89931a1bc@embeddedor.com> (raw)
In-Reply-To: <20190218211422.3518C21900@mail.kernel.org>
Hi Sasha,
On 2/18/19 3:14 PM, Sasha Levin wrote:
> Hi,
>
> [This is an automated email]
>
> This commit has been processed because it contains a "Fixes:" tag,
> fixing commit: 58dd7c0a2a6e Staging: comedi: add ni_660x driver.
>
> The bot has tested the following trees: v4.20.8, v4.19.21, v4.14.99, v4.9.156, v4.4.174, v3.18.134.
>
> v4.20.8: Build OK!
> v4.19.21: Build OK!
> v4.14.99: Build OK!
> v4.9.156: Build OK!
> v4.4.174: Failed to apply! Possible dependencies:
> 01ead0ded315 ("staging: comedi: ni_660x: cleanup the NI660X_IO_CFG register helpers")
> 22acd860137a ("staging: comedi: ni_660x: change IOConfigReg() into a macro")
> 41014593caeb ("staging: comedi: ni_660x: cleanup the NI660X_GLOBAL_INT_{STATUS, CFG}")
> 502552e161ae ("staging: comedi: ni_660x: remove enum clock_config_register_bits")
> 518d38423b48 ("staging: comedi: ni_660x: tidy up ni_660x_select_pfi_output()")
> 9678b73e273a ("staging: comedi: ni_660x: tidy up ni_660x_write_register()")
> aa94f2888825 ("staging: comedi: ni_660x: tidy up ni_660x_set_pfi_routing()")
> ad98c18cb9de ("staging: comedi: ni_660x: tidy up ni_660x_read_register()")
> cded944fa90c ("staging: comedi: ni_660x: Prefer kernel type 'u64' over 'uint64_t'")
> fecf4cce0021 ("staging: comedi: ni_660x: cleanup the NI660X_DMA_CFG register helpers")
>
> v3.18.134: Failed to apply! Possible dependencies:
> 01ead0ded315 ("staging: comedi: ni_660x: cleanup the NI660X_IO_CFG register helpers")
> 22acd860137a ("staging: comedi: ni_660x: change IOConfigReg() into a macro")
> 41014593caeb ("staging: comedi: ni_660x: cleanup the NI660X_GLOBAL_INT_{STATUS, CFG}")
> 502552e161ae ("staging: comedi: ni_660x: remove enum clock_config_register_bits")
> 518d38423b48 ("staging: comedi: ni_660x: tidy up ni_660x_select_pfi_output()")
> 9678b73e273a ("staging: comedi: ni_660x: tidy up ni_660x_write_register()")
> aa94f2888825 ("staging: comedi: ni_660x: tidy up ni_660x_set_pfi_routing()")
> ad98c18cb9de ("staging: comedi: ni_660x: tidy up ni_660x_read_register()")
> cded944fa90c ("staging: comedi: ni_660x: Prefer kernel type 'u64' over 'uint64_t'")
> fecf4cce0021 ("staging: comedi: ni_660x: cleanup the NI660X_DMA_CFG register helpers")
>
>
> How should we proceed with this patch?
>
Ian commented that this bug was introduced in 4.7, so it should be applied to 4.9 ... 4.20
Thanks
--
Gustavo
prev parent reply other threads:[~2019-02-18 21:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-12 18:08 [PATCH] staging: comedi: ni_660x: fix missing break in switch statement Gustavo A. R. Silva
2019-02-12 18:46 ` Gustavo A. R. Silva
[not found] ` <20190215154828.DE5DF222A1@mail.kernel.org>
2019-02-15 17:43 ` Ian Abbott
[not found] ` <20190218211422.3518C21900@mail.kernel.org>
2019-02-18 21:19 ` Gustavo A. R. Silva [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=8b7905e6-6e77-d473-fb6a-55e89931a1bc@embeddedor.com \
--to=gustavo@embeddedor.com \
--cc=abbotti@mev.co.uk \
--cc=devel@driverdev.osuosl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sashal@kernel.org \
--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 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).