Raspberry Pi's firmware controls this pll, we should use the firmware
interface to access it.
Signed-off-by: Nicolas Saenz Julienne
Acked-by: Eric Anholt
---
Changes since v1:
- Add comment to explain why pllb isn't there anymore
drivers/clk/bcm/clk-bcm2835.c | 28
Hi all,
this aims at adding cpufreq support to the Raspberry Pi family of
boards.
The series first factors out 'pllb' from clk-bcm2385 and creates a new
clk driver that operates it over RPi's firmware interface[1]. We are
forced to do so as the firmware 'owns' the pll and we're not allowed to
On 05.06.19 21:23, Christoph Hellwig wrote:
> On Wed, Jun 05, 2019 at 01:36:25PM +0200, Enrico Weigelt, metux IT consult
> wrote:
>> Hello folks,
>>
>>
>> here's a patchset that allows enabling libata's tpm features (opal)
>> at runtime. Until now we need to boot with special kernel parameter,
>>
On Thu, 6 Jun 2019, Andrea Parri wrote:
> This seems a sensible change to me: looking forward to seeing a patch,
> on top of -rcu/dev, for further review and testing!
>
> We could also add (to LKMM) the barrier() for rcu_read_{lock,unlock}()
> discussed in this thread (maybe once the RCU code
On Thu, 6 Jun 2019 16:00:01 +0200
Vitor Soares wrote:
> Currently the I3C framework limits SCL frequency to FM speed when
> dealing with a mixed slow bus, even if all I2C devices are FM+ capable.
>
> The core was also not accounting for I3C speed limitations when
> operating in mixed slow mode
On Thu, 6 Jun 2019, Kai-Heng Feng wrote:
> at 15:55, Kai-Heng Feng wrote:
>
> > at 18:22, Kai-Heng Feng wrote:
> >
> >> at 00:01, Kai-Heng Feng wrote:
> >>
> On Jan 30, 2019, at 16:21, Greg KH wrote:
>
> On Thu, Jan 24, 2019 at 02:16:43PM +0800, Kai-Heng Feng wrote:
> >
On Mon, May 06, 2019 at 04:29:39PM -0700, rcampb...@nvidia.com wrote:
> From: Ralph Campbell
>
> There are no functional changes, just some coding style clean ups and
> minor comment changes.
>
> Signed-off-by: Ralph Campbell
> Reviewed-by: Jérôme Glisse
> Cc: John Hubbard
> Cc: Ira Weiny
>
On 06/06/2019 13:17, Vivek Gautam wrote:
> <_smmu 0x6c0 0x3> // for both 0x6c0 (TZ) and 0x6c3 (HLOS)
Another possibility is to list both:
<_smmu 0x6c0 0x0>
<_smmu 0x6c3 0x0>
which leaves 0x6c1 and 0x6c2 out of the picture, and makes 0x6c3
appear explicitly (for anyone
Hi Arnaldo,
On Thu, Jun 06, 2019 at 10:38:38AM -0300, Arnaldo Carvalho de Melo wrote:
> Em Thu, Jun 06, 2019 at 05:48:44PM +0800, Leo Yan escreveu:
> > This patch adds support for arm64 raw syscall numbers so that we can use
> > it on arm64 platform.
> >
> > After applied this patch, we need to
On Sat, May 25, 2019 at 12:37:23PM +0100, Dragan Cvetic wrote:
> SD-FEC statistic data are:
> - count of data interface errors (isr_err_count)
> - count of Correctable ECC errors (cecc_count)
> - count of Uncorrectable ECC errors (uecc_count)
>
> Add support:
> 1. clear stats ioctl callback which
On 2019/6/6 AM 4:06, bseg...@google.com wrote:
> When a cfs_rq sleeps and returns its quota, we delay for 5ms before
> waking any throttled cfs_rqs to coalesce with other cfs_rqs going to
> sleep, as this has has to be done outside of the rq lock we hold.
two "has".
>
> The current code waits
Now that restore_saved_sigmask_unless() is always called with the same
argument right before poll_select_copy_remaining() we can move it into
poll_select_copy_remaining() and make it the only caller of restore()
in fs/select.c.
The patch also renames poll_select_copy_remaining(),
do_poll() returns -EINTR if interrupted and after that all its callers
have to translate it into -ERESTARTNOHAND. Change do_poll() to return
-ERESTARTNOHAND and update (simplify) the callers.
Note that this also unifies all users of restore_saved_sigmask_unless(),
see the next patch.
Lets start from fs/select.c
I have no idead how to test these changes, please review.
On top of "[PATCH -mm V2 1/1] signal: simplify
set_user_sigmask/restore_user_sigmask"
it seems that we can do more unrelated cleanups in this code, say,
poll_select_prepare(enum poll_time_type pt_type).
Em Thu, Jun 06, 2019 at 05:48:45PM +0800, Leo Yan escreveu:
> To build this program successfully with clang, there have three
> compiler options need to be specified:
>
> - Header file path: tools/perf/include/bpf;
> - Specify architecture;
> - Define macro __NR_CPUS__.
So, this shouldn't
Em Thu, Jun 06, 2019 at 10:46:24AM -0300, Arnaldo Carvalho de Melo escreveu:
> Em Thu, Jun 06, 2019 at 10:38:38AM -0300, Arnaldo Carvalho de Melo escreveu:
> > Em Thu, Jun 06, 2019 at 05:48:44PM +0800, Leo Yan escreveu:
> > > This patch adds support for arm64 raw syscall numbers so that we can use
On 6/6/19 9:16 AM, David Howells wrote:
Stephen Smalley wrote:
This might be easier to discuss if you can reply to:
https://lore.kernel.org/lkml/5393.1559768...@warthog.procyon.org.uk/
which is on the ver #2 posting of this patchset.
Sorry for being late to the party. Not sure
On Mon, May 06, 2019 at 04:29:38PM -0700, rcampb...@nvidia.com wrote:
> From: Ralph Campbell
>
> Update the HMM documentation to reflect the latest API and make a few minor
> wording changes.
>
> Signed-off-by: Ralph Campbell
> Reviewed-by: Jérôme Glisse
> Cc: John Hubbard
> Cc: Ira Weiny
>
On 6/6/19 4:39 AM, Dmitry Osipenko wrote:
06.06.2019 10:35, Bitan Biswas пишет:
Fix checkpatch.pl warning(s)/error(s)/check(s) in i2c-tegra.c
Remove redundant BUG_ON calls or replace with WARN_ON_ONCE
as needed. Replace BUG() with error handling code.
Define I2C_ERR_UNEXPECTED_STATUS for
On 3/06/19 9:37 PM, Douglas Anderson wrote:
> There are certain cases, notably when transitioning between sleep and
> active state, when Broadcom SDIO WiFi cards will produce errors on the
> SDIO bus. This is evident from the source code where you can see that
> we try commands in a loop until we
The i3c bus spec defines a bus configuration where i2c devices don't
have a 50ns filter but support SCL running at SDR max rate (12.5MHz).
This patch introduces the limited bus mode so that users can use
a higher speed in presence of i2c devices index 1.
Signed-off-by: Vitor Soares
Cc: Boris
This patch add limited bus mode support for DesignWare i3c master
Signed-off-by: Vitor Soares
Cc: Boris Brezillon
Cc:
---
Changes in v2:
None
drivers/i3c/master/dw-i3c-master.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/i3c/master/dw-i3c-master.c
Currently the I3C framework limits SCL frequency to FM speed when
dealing with a mixed slow bus, even if all I2C devices are FM+ capable.
The core was also not accounting for I3C speed limitations when
operating in mixed slow mode and was erroneously using FM+ speed as the
max I2C speed when
On 6/6/19 5:06 AM, Dmitry Osipenko wrote:
06.06.2019 8:54, Bitan Biswas пишет:
Post suspend I2C registers have power on reset values. Before any
transfer initialize I2C registers to prevent I2C transfer timeout
and implement suspend and resume callbacks needed. Fix below errors
post suspend:
The powerpc's flush_cache_vmap() is defined as a macro and never use
both of its arguments, so it will generate a compilation warning,
lib/ioremap.c: In function 'ioremap_page_range':
lib/ioremap.c:203:16: warning: variable 'start' set but not used
[-Wunused-but-set-variable]
Fix it by making it
On 6/5/19 18:53, Lukasz Luba wrote:
> Lukasz Luba (13):
> clk: samsung: add needed IDs for DMC clocks in Exynos5420
> clk: samsung: add new clocks for DMC for Exynos5422 SoC
> clk: samsung: add BPLL rate table for Exynos 5422 SoC
> dt-bindings: ddr: rename lpddr2 directory
> dt-bindings:
Hi Arnaldo,
On Thu, Jun 06, 2019 at 10:30:19AM -0300, Arnaldo Carvalho de Melo wrote:
> Em Thu, Jun 06, 2019 at 05:48:42PM +0800, Leo Yan escreveu:
> > On my Juno board with ARM64 CPUs, perf trace command reports the eBPF
> > program building failure but the command will not exit and continue to
On 6/6/19 4:52 AM, Dmitry Osipenko wrote:
06.06.2019 8:43, Bitan Biswas пишет:
On 5/31/19 5:43 AM, Dmitry Osipenko wrote:
31.05.2019 11:50, Bitan Biswas пишет:
On 5/30/19 4:27 AM, Dmitry Osipenko wrote:
30.05.2019 8:55, Bitan Biswas пишет:
Post suspend I2C registers have power on
06.06.2019 16:45, Dmitry Osipenko пишет:
> 06.06.2019 15:37, Jon Hunter пишет:
>>
>> On 06/06/2019 12:54, Peter Ujfalusi wrote:
>>>
>>>
>>> On 06/06/2019 13.49, Jon Hunter wrote:
On 06/06/2019 11:22, Peter Ujfalusi wrote:
...
It does sounds like that FIFO_SIZE ==
Hello,
syzbot found the following crash on:
HEAD commit:156c0591 Merge tag 'linux-kselftest-5.2-rc4' of git://git...
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=15f2095aa0
kernel config: https://syzkaller.appspot.com/x/.config?x=60564cb52ab29d5b
This patch removes all haphazard code implementing nocow writers
exclusion from pending snapshot creation and switches to using the drw
lock to ensure this invariant still holds. "Readers" are snapshot
creators from create_snapshot and 'writers' are nocow writers from
buffered write path or
Hello,
syzbot found the following crash on:
HEAD commit:156c0591 Merge tag 'linux-kselftest-5.2-rc4' of git://git...
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=13512d51a0
kernel config: https://syzkaller.appspot.com/x/.config?x=60564cb52ab29d5b
A (D)ouble (R)eader (W)riter lock is a locking primitive that allows
to have multiple readers or multiple writers but not multiple readers
and writers holding it concurrently. The code is factored out from
the existing open-coded locking scheme used to exclude pending
snapshots from nocow writers
On Thu, Jun 06, 2019 at 09:42:33PM +0800, Herbert Xu wrote:
> On Thu, Jun 06, 2019 at 06:19:33AM -0700, Paul E. McKenney wrote:
> > Commit bb73c52bad36 ("rcu: Don't disable preemption for Tiny and Tree
> > RCU readers") removed the barrier() calls from rcu_read_lock() and
> > rcu_write_lock() in
Hello,
syzbot found the following crash on:
HEAD commit:f75e4cfe kmsan: use kmsan_handle_urb() in urb.c
git tree: kmsan
console output: https://syzkaller.appspot.com/x/log.txt?x=153453dea0
kernel config: https://syzkaller.appspot.com/x/.config?x=602468164ccdc30a
dashboard link:
On Thu, Jun 06, 2019 at 09:38:24PM +0800, Herbert Xu wrote:
> On Thu, Jun 06, 2019 at 03:58:17AM -0700, Paul E. McKenney wrote:
> >
> > I cannot immediately think of a way that the compiler could get this
> > wrong even in theory, but similar code sequences can be messed up.
> > The reason for
Em Thu, Jun 06, 2019 at 10:38:38AM -0300, Arnaldo Carvalho de Melo escreveu:
> Em Thu, Jun 06, 2019 at 05:48:44PM +0800, Leo Yan escreveu:
> > This patch adds support for arm64 raw syscall numbers so that we can use
> > it on arm64 platform.
> >
> > After applied this patch, we need to specify
06.06.2019 15:37, Jon Hunter пишет:
>
> On 06/06/2019 12:54, Peter Ujfalusi wrote:
>>
>>
>> On 06/06/2019 13.49, Jon Hunter wrote:
>>>
>>> On 06/06/2019 11:22, Peter Ujfalusi wrote:
>>>
>>> ...
>>>
>>> It does sounds like that FIFO_SIZE == src/dst_maxburst in your case as
>>> well.
>>
On Thu, Jun 06, 2019 at 10:31:56AM +, Jisheng Zhang wrote:
> Move the reset gpio dt parse and request to stmmac_mdio_register(),
> thus makes the mdio code straightforward.
>
> This patch also replace stack var mdio_bus_data with data to simplify
> the code.
Hi Jisheng
Please split this
On Tue, May 28, 2019 at 01:11:42PM +0800, Paul Wise wrote:
> Save the offsets of the start of each argument to avoid having to
> update pointers to each argument after every corename krealloc and
> to avoid having to duplicate the memory for the dump command.
>
> Executable names containing
Hi Linus,
Please pull from:
git://git.kernel.org/pub/scm/linux/kernel/git/mszeredi/vfs.git
tags/ovl-fixes-5.2-rc4
Here's one fix for a class of bugs triggered by syzcaller, and one that
makes xfstests fail less.
Thanks,
Miklos
On 06.06.2019 16:13, J. Bruce Fields wrote:
> On Thu, Jun 06, 2019 at 10:47:43AM +0300, Kirill Tkhai wrote:
>> This may be connected with that shrinker unregistering is forgotten on error
>> path.
>
> I was wondering about that too. Seems like it would be hard to hit
> reproduceably though: one
On Thu, Jun 06, 2019 at 06:19:33AM -0700, Paul E. McKenney wrote:
> Commit bb73c52bad36 ("rcu: Don't disable preemption for Tiny and Tree
> RCU readers") removed the barrier() calls from rcu_read_lock() and
> rcu_write_lock() in CONFIG_PREEMPT=n&_PREEMPT_COUNT=n kernels.
> Within RCU, this commit
Hi everyone,
[V7] The Driver was moved to staging until it can pass future
specification & compliance tools.
[V6] Good news, the firmware situation is resolved. We have received a
redistributable license from Amlogic and the firmwares have been merged
in linux-firmware[5].
[V5] It's been a
Add an entry for the meson video decoder for amlogic SoCs.
Signed-off-by: Maxime Jourdan
---
MAINTAINERS | 8
1 file changed, 8 insertions(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index b8fbf41865c2..7cf3ece9f0cb 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -10222,6 +10222,14 @@ S:
Amlogic SoCs feature a powerful video decoder unit able to
decode many formats, with a performance of usually up to 4k60.
This is a driver for this IP that is based around the v4l2 m2m framework.
It features decoding for:
- MPEG 1
- MPEG 2
Supported SoCs are: GXBB (S905), GXL (S905X/W/D), GXM
Add documentation for the meson vdec dts node.
Signed-off-by: Maxime Jourdan
Reviewed-by: Rob Herring
---
.../bindings/media/amlogic,vdec.txt | 71 +++
1 file changed, 71 insertions(+)
create mode 100644 Documentation/devicetree/bindings/media/amlogic,vdec.txt
diff
On Thu, 6 Jun 2019 at 06:11, Richard Cochran wrote:
>
> On Wed, Jun 05, 2019 at 09:08:54PM +0300, Vladimir Oltean wrote:
> > Currently I'm using a cyclecounter, but I *will* need actual PHC
> > manipulations for the time-based shaping and policing features that
> > the switch has in hardware.
>
>
Em Thu, Jun 06, 2019 at 05:48:44PM +0800, Leo Yan escreveu:
> This patch adds support for arm64 raw syscall numbers so that we can use
> it on arm64 platform.
>
> After applied this patch, we need to specify macro -D__aarch64__ or
> -D__x86_64__ in compilation option so Clang can use the
On Thu, Jun 06, 2019 at 03:58:17AM -0700, Paul E. McKenney wrote:
>
> I cannot immediately think of a way that the compiler could get this
> wrong even in theory, but similar code sequences can be messed up.
> The reason for this is that in theory, the compiler could use the
> stored-to location
Hi Linus,
Please pull from:
git://git.kernel.org/pub/scm/linux/kernel/git/mszeredi/fuse.git
tags/fuse-fixes-5.2-rc4
This fixes a leaked inode lock in an error cleanup path and a data
consistency issue with copy_file_range(). It also adds a new flag for the
WRITE request that allows
On 6/6/19 1:45 PM, Krzysztof Kozlowski wrote:
> On Thu, 6 Jun 2019 at 12:38, Lukasz Luba wrote:
>> Hi Krzysztof,
+/**
+ * exynos5_dmc_init_clks() - Initialize clocks needed for DMC operation.
+ * @dmc: DMC structure containing needed fields
+ *
+ * Get the needed
Em Thu, Jun 06, 2019 at 10:30:19AM -0300, Arnaldo Carvalho de Melo escreveu:
> Em Thu, Jun 06, 2019 at 05:48:42PM +0800, Leo Yan escreveu:
> > +++ b/tools/perf/builtin-trace.c
> > @@ -3664,6 +3664,14 @@ static int trace__config(const char *var, const char
> > *value, void *arg)
> >
On Tue, Apr 23, 2019 at 12:50:46PM +0200, Simon Horman wrote:
> On Tue, Apr 23, 2019 at 07:09:58PM +0900, Nguyen An Hoan wrote:
> > From: Hoan Nguyen An
> >
> > Add r8a77965 DRIF bindings.
> >
> > Signed-off-by: Hoan Nguyen An
>
> According to the User's Manual Hardware, v1.50 Nov 20 2019,
>
Em Thu, Jun 06, 2019 at 05:48:42PM +0800, Leo Yan escreveu:
> On my Juno board with ARM64 CPUs, perf trace command reports the eBPF
> program building failure but the command will not exit and continue to
> run. If we define an eBPF event in config file, the event will be
> parsed with below
On 06/06/2019 14:24, Amadeusz Sławiński wrote:
+ SOC_SINGLE_SX_TLV("IIR1 INP1 Volume",
LPASS_CDC_IIR1_GAIN_B1_CTL,
+ 0, -84, 40, digital_gain),
+ SOC_SINGLE_SX_TLV("IIR1 INP2 Volume",
LPASS_CDC_IIR1_GAIN_B2_CTL,
+ 0, -84, 40,
On Sat, May 25, 2019 at 12:37:17PM +0100, Dragan Cvetic wrote:
> +static int xsdfec_dev_open(struct inode *iptr, struct file *fptr)
> +{
> + return 0;
> +}
> +
> +static int xsdfec_dev_release(struct inode *iptr, struct file *fptr)
> +{
> + return 0;
> +}
empty open/close functions are
On Fri 2019-05-31 14:39:08, Josh Poimboeuf wrote:
> On Fri, May 31, 2019 at 09:41:47AM +0200, Petr Mladek wrote:
> > The err_buf array uses 128 bytes of stack space. Move it off the stack
> > by making it static. It's safe to use a shared buffer because
> > klp_try_switch_task() is called under
On Sat, May 25, 2019 at 12:37:17PM +0100, Dragan Cvetic wrote:
> Add char device interface per DT node present and support
> file operations:
> - open(),
> - close(),
> - unlocked_ioctl(),
> - compat_ioctl().
>
> Tested-by: Dragan Cvetic
> Signed-off-by: Derek Kiernan
> Signed-off-by: Dragan
On Sat, May 25, 2019 at 12:37:15PM +0100, Dragan Cvetic wrote:
> Implements an platform driver that matches with xlnx,
> sd-fec-1.1 device tree node and registers as a character
> device, including:
> - SD-FEC driver binds to sdfec DT node.
> - creates and initialise an initial driver dev
Hi Hans,
On Thu, Jun 6, 2019 at 2:32 PM Hans Verkuil wrote:
>
> While preparing this series for merging I came across the following checkpatch
> and sparse warnings:
>
> checkpatch:
>
> CHECK: Alignment should match open parenthesis
> #159: FILE:
On Thu, Jun 06, 2019 at 10:08:50AM +0200, Jesper Dangaard Brouer wrote:
On Wed, 05 Jun 2019 12:14:50 -0700 (PDT)
David Miller wrote:
From: Ivan Khoronzhuk
Date: Wed, 5 Jun 2019 16:20:02 +0300
> This patchset adds XDP support for TI cpsw driver and base it on
> page_pool allocator. It was
From: Oleg Nesterov
> Sent: 06 June 2019 13:41
> On 06/06, David Laight wrote:
> >
> > Some of this code is hard to grep through :-)
>
> I'd suggest to simply read the kernel code once and memorise it, after
> that you will not need to use grep.
Unfortunately all the available buffer space is
On Mon, 3 Jun 2019 09:32:42 -0700
Florian Fainelli wrote:
Hi,
> On 6/3/19 1:30 AM, peng@nxp.com wrote:
> > From: Peng Fan
> >
> > This mailbox driver implements a mailbox which signals transmitted data
> > via an ARM smc (secure monitor call) instruction. The mailbox receiver
> > is
On Thu, 6 Jun 2019 13:42:42 +0100
Srinivas Kandagatla wrote:
> This patch adds sidetone support via one of the 3 RX Mix paths
> using IIR1 and IIR2.
> IIR1 can be feed by any Decimators or RX paths, and IIRx can also be
> looped back to RX mixers to provide sidetone functionality.
> Two IIR
Commit bb73c52bad36 ("rcu: Don't disable preemption for Tiny and Tree
RCU readers") removed the barrier() calls from rcu_read_lock() and
rcu_write_lock() in CONFIG_PREEMPT=n&_PREEMPT_COUNT=n kernels.
Within RCU, this commit was OK, but it failed to account for things like
get_user() that can
Marc
Bump
On 5/31/19 6:51 AM, Dan Murphy wrote:
Marc
On 5/15/19 3:54 PM, Dan Murphy wrote:
Marc
On 5/9/19 11:11 AM, Dan Murphy wrote:
Create a m_can platform framework that peripheral
devices can register to and use common code and register sets.
The peripheral devices may provide
I have at least these 2 instances:
In file included from
/tmp/e2/build/linux-4.9.180/include/drm/drm_vma_manager.h:28,
from /tmp/e2/build/linux-4.9.180/include/drm/drmP.h:78,
from
/tmp/e2/build/linux-4.9.180/include/drm/drm_modeset_helper.h:26,
On Thu, Jun 06, 2019 at 10:32:16AM +0300, Oded Gabbay wrote:
> Hi Greg,
>
> This is a pull request containing fixes to be merged to 5.2-rc4/5.
>
> It contains 3 bug fixes. See the tag comment for more details.
>
> Thanks,
> Oded
>
> The following changes since commit
Hi!
(stable removed from cc list)
> static void mmc_pwrseq_emmc_reset(struct mmc_host *host)
> {
> struct mmc_pwrseq_emmc *pwrseq = to_pwrseq_emmc(host->pwrseq);
>
> - __mmc_pwrseq_emmc_reset(pwrseq);
> + gpiod_set_value_cansleep(pwrseq->reset_gpio, 1);
> + udelay(1);
> +
On Thu, Jun 06, 2019 at 10:47:43AM +0300, Kirill Tkhai wrote:
> This may be connected with that shrinker unregistering is forgotten on error
> path.
I was wondering about that too. Seems like it would be hard to hit
reproduceably though: one of the later allocations would have to fail,
then
(stable removed from cc list)
> Indio->mlock is used for protecting the different iio device modes.
> It is currently not being used in this way. Replace the lock with
> an internal lock specifically used for protecting the SPI transfer
> buffer.
>
> Signed-off-by: Justin Chen
> Signed-off-by:
From: Colin Ian King
The u32 variable rem is being shifted using u32 arithmetic however
it is being passed to div_u64 that expects the expression to be a u64.
The 32 bit shift may potentially overflow, so cast rem to a u64 before
shifting to avoid this.
Addresses-Coverity: ("Unintentional
Hi!
(stable removed from cc).
> [ Upstream commit 67a0514afdbb8b2fc70b771b8c77661a9cb9d3a9 ]
>
> Objtool spotted that we call native_load_gs_index() with AC set.
> Re-arrange the code to avoid that.
Does this introduce undefined behaviour?
>
> @@ -72,6 +71,7 @@ static int
On Wed, Jun 05, 2019 at 06:59:52PM -0700, Shobhit Kukreti wrote:
> Cleaned up the code to remove the error "(foo*)" should be "(foo *)"
> reported by checkpatch from the file rtl8723bs/os_dep/ioctl_linux.c
Your subject line shoudl give a hint as to what the error you are fixing
is.
Also, no need
On Tue, Jun 04, 2019 at 09:51:36AM +0530, Deepak Mishra wrote:
> This patch renames CamelCase variable wkFilterRxFF0 to wk_filter_rx_ff0
> in drv_types.h and related files rtl871x_xmit.c and xmit_linux.c as
> reported by checkpatch.pl
>
> This patch renames CamelCase variable lockRxFF0Filter to
On Tue, Jun 04, 2019 at 09:51:34AM +0530, Deepak Mishra wrote:
> This patch renames CamelCase cmdThread to cmd_thread in struct _adapter and
> related
> files drv_types.h,os_intfs.c
> CHECK: Avoid CamelCase:
What is this "CHECK:" line from?
thanks,
greg k-h
On Tue, Jun 04, 2019 at 09:51:33AM +0530, Deepak Mishra wrote:
> This patch renames CamelCase EepromAddressSizefrom to eeprom_address_size in
> struct _adapter and in related files drv_types.h, rtl871x_eeprom.c, usb_intf.c
>
> CHECK: Avoid CamelCase:
>
> This patch removed unused variable
On Tue, Jun 04, 2019 at 01:42:22PM +0530, Nishka Dasgupta wrote:
> Remove function rtw_free_network_nolock, as all it does is call
> _rtw_free_network_nolock, and rename _rtw_free_network_nolock to
> rtw_free_network_nolock.
>
> Signed-off-by: Nishka Dasgupta
> ---
>
On Thu, Jun 06, 2019 at 08:24:41AM +0200, Christoph Hellwig wrote:
> On Wed, Jun 05, 2019 at 05:22:35PM -0300, Jason Gunthorpe wrote:
> > On Wed, Jun 05, 2019 at 09:08:31PM +0200, Christoph Hellwig wrote:
> > > This ensures all proper DMA layer handling is taken care of by the
> > > SCSI midlayer.
On 03/06/2019 20:29, Mathieu Poirier wrote:
On Thu, May 30, 2019 at 05:54:24PM +0100, Suzuki K Poulose wrote:
Instead of using smp_processor_id() to figure out the node,
use the numa_node_id() for the current CPU node to avoid
splats like :
I was in the process of applying this set when I
On 6/6/19 2:41 PM, Dan Carpenter wrote:
> The problem is that on 64bit systems then we don't clear the higher
> bits of the "pending" variable. So when we do:
>
> ack = pending & ~BIT(STMFX_REG_IRQ_SRC_EN_GPIO);
> if (ack) {
>
> the if (ack) condition relies on uninitialized
On 03/06/2019 11:07, Mike Leach wrote:
Hi,
On Wed, 22 May 2019 at 11:37, Suzuki K Poulose wrote:
The CoreSight components ETM and CPU-Debug are always associated
with CPUs. Replace the of_coresight_get_cpu() with a platform
agnostic helper, in preparation to add ACPI support.
On Tue, Jun 04, 2019 at 12:29:13AM +0200, Simon Sandström wrote:
> Fixes checkpatch.pl warning "Prefer using '"%s...", __func__' to using
> '', this function's name, in a string".
>
> Signed-off-by: Simon Sandström
> ---
> drivers/staging/kpc2000/kpc2000/core.c | 10 +-
> 1 file
On Wed, 5 Jun 2019 10:06:47 -0500
Pierre-Louis Bossart wrote:
> On 6/5/19 8:45 AM, Amadeusz Sławiński wrote:
> > During the integration of HDaudio support, we changed the way in
> > which we get hdev in snd_hdac_ext_bus_device_init() to use one
> > preallocated with devm_kzalloc(), however it
Hi!
> [ Upstream commit faf5a744f4f8d76e7c03912b5cd381ac8045f6ec ]
>
> clang -Wuninitialized incorrectly sees a variable being used without
> initialization:
>
> drivers/scsi/lpfc/lpfc_nvme.c:2102:37: error: variable 'localport' is
> uninitialized when used here
>
On Wed, Jun 05, 2019 at 07:51:12PM -0500, Jassi Brar wrote:
> On Wed, Jun 5, 2019 at 2:46 PM Mark Brown wrote:
> >
> > On Tue, Jun 04, 2019 at 10:44:24AM +0100, Sudeep Holla wrote:
> > > On Mon, Jun 03, 2019 at 08:39:46PM +0100, Mark Brown wrote:
> >
> > >
> > > > It feels like the issues with
Hi!
> [ Upstream commit 0ab34a08812a3334350dbaf69a018ee0ab3d2ddd ]
>
> si2165_readreg8() may fail. Looking into si2165_readreg8(), we will find
> that "val_tmp" will be an uninitialized value when regmap_read() fails.
> "val_tmp" is then assigned to "val". So if si2165_readreg8() fails,
> "val"
On Mon, Jun 03, 2019 at 05:37:17PM +0200, Jernej Škrabec wrote:
> Dne ponedeljek, 03. junij 2019 ob 13:55:36 CEST je Maxime Ripard napisal(a):
> > int current = 0;
> >
> > while (current < num) {
> > int tmp = min(num - current, 32);
> >
> > cedrus_write(dev, VE_H264_TRIGGER_TYPE, 0x3 |
This patch adds sidetone support via one of the 3 RX Mix paths
using IIR1 and IIR2.
IIR1 can be feed by any Decimators or RX paths, and IIRx can also be
looped back to RX mixers to provide sidetone functionality.
Two IIR filters are used for Side tone equalization and each filter
is 5 stage.
The problem is that on 64bit systems then we don't clear the higher
bits of the "pending" variable. So when we do:
ack = pending & ~BIT(STMFX_REG_IRQ_SRC_EN_GPIO);
if (ack) {
the if (ack) condition relies on uninitialized data. The fix it that
I've changed "pending" from an
Hi Hans,
Thanks for reviewing.
> -Original Message-
> From: Hans Verkuil [mailto:hverk...@xs4all.nl]
> Sent: Wednesday, June 05, 2019 6:14 PM
> To: Vishal Sagar ; Hyun Kwon ;
> laurent.pinch...@ideasonboard.com; mche...@kernel.org;
> robh...@kernel.org; mark.rutl...@arm.com; Michal Simek
On 06/06, David Laight wrote:
>
> Some of this code is hard to grep through :-)
I'd suggest to simply read the kernel code once and memorise it, after
that you will not need to use grep.
> > When signal handler returns it does sys_rt_sigreturn() which restores
> > the original mask saved in
Device that bound to XDP socket will not have zero refcount until the
userspace application will not close it. This leads to hang inside
'netdev_wait_allrefs()' if device unregistering requested:
# ip link del p1
< hang on recvmsg on netlink socket >
# ps -x | grep ip
5126 pts/0D+
On 06/06/2019 12:54, Peter Ujfalusi wrote:
>
>
> On 06/06/2019 13.49, Jon Hunter wrote:
>>
>> On 06/06/2019 11:22, Peter Ujfalusi wrote:
>>
>> ...
>>
>> It does sounds like that FIFO_SIZE == src/dst_maxburst in your case as
>> well.
> Not exactly equal.
> ADMA burst_size can
> On 6 Jun 2019, at 15:33, Paolo Bonzini wrote:
>
> Make it available to AMD hosts as well, just in case someone is trying
> to use an Intel processor's CPUID setup.
I’m actually quite surprised that such a setup works properly.
>
> Suggested-by: Sean Christopherson
> Signed-off-by: Paolo
Make it available to AMD hosts as well, just in case someone is trying
to use an Intel processor's CPUID setup.
Suggested-by: Sean Christopherson
Signed-off-by: Paolo Bonzini
---
arch/x86/include/asm/kvm_host.h | 1 +
arch/x86/kvm/vmx/vmx.c | 6 --
arch/x86/kvm/vmx/vmx.h
On 6/5/19 6:18 PM, Maxime Jourdan wrote:
> Amlogic SoCs feature a powerful video decoder unit able to
> decode many formats, with a performance of usually up to 4k60.
>
> This is a driver for this IP that is based around the v4l2 m2m framework.
>
> It features decoding for:
> - MPEG 1
> - MPEG 2
From: Colin Ian King
Currently the return from the call to nct7904_read is being masked
and so and negative error returns are being stripped off and the
error check is always false. Fix this by checking on err first and
then masking the return value in ret.
Addresses-Coverity: ("Logically dead
On Thu, Jun 06, 2019 at 05:28:55PM +0800, Herbert Xu wrote:
> On Thu, Jun 06, 2019 at 02:06:19AM -0700, Paul E. McKenney wrote:
> >
> > Or is your point instead that given the initial value of "a" being
> > zero and the value stored to "a" being one, there is no way that
> > any possible load and
501 - 600 of 941 matches
Mail list logo
