From: Markus Elfring
Date: Sun, 17 Sep 2017 08:32:17 +0200
Replace the specification of data structures by variable references
as the parameter for the operator "sizeof" to make the corresponding size
determination a bit safer according to the Linux coding style convention.
Signed-off-by: Markus
From: Markus Elfring
Date: Sun, 17 Sep 2017 08:20:04 +0200
Omit an extra message for a memory allocation failure in this function.
This issue was detected by using the Coccinelle software.
Signed-off-by: Markus Elfring
---
drivers/media/tuners/si2157.c | 1 -
1 file changed, 1 deletion(-)
di
From: Markus Elfring
Date: Sun, 17 Sep 2017 08:48:24 +0200
Two update suggestions were taken into account
from static source code analysis.
Markus Elfring (2):
Delete an error message for a failed memory allocation
Improve a size determination in two functions
drivers/media/tuners/si2157.c
Hi Rik,
On Thu, Sep 14, 2017 at 8:56 AM, Rik van Riel wrote:
> On Sun, 2017-09-10 at 23:32 -0700, Joel Fernandes wrote:
>>
>> To make the load check more meaningful, I am thinking if using
>> wake_affine()'s balance check is a better thing to do than the
>> 'nr_running < 2' check I used in this p
On (09/06/17 09:55), Petr Mladek wrote:
[..]
> > but I'm not super eager to have printk-safe based buffering.
> > that's why I never posted a patch set. this approach has its
> > limitations.
>
> Ah, I am happy to read this. From the previous mails,
> I got the feeling that you were eager to go th
Hi Rob,
FYI, the error/warning still remains.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: 2bd6bf03f4c1c59381d62c61d03f6cc3fe71f66e
commit: 0ae349a0f33fb040a2bc228fdc6d60111455feab iommu/qcom: Add qcom_iommu
date: 5 weeks ago
config: m32r-allmodconf
On 09/17/2017 06:30 AM, Paul E. McKenney wrote:
On Fri, Sep 15, 2017 at 04:44:38PM +0530, Neeraj Upadhyay wrote:
Hi,
We have one query regarding the behavior of RCU expedited grace period,
for scenario where resched_cpu() in sync_sched_exp_handler() fails to
acquire the rq lock and returns w/
Hi Jason,
On Sat, Sep 16, 2017 at 03:05:33PM +0200, Jason A. Donenfeld wrote:
> -
> - ret = big_key_gen_enckey(enckey);
> - if (ret)
> - goto err_enckey;
> + ret = get_random_bytes_wait(enckey, ENC_KEY_SIZE);
> + if (unlikely(ret)
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
2bd6bf03f4c1c59381d62c61d03f6cc3fe71f66e Linux 4.14-rc1
arch/alpha/include/asm/mmu_context.h:160:24: error: invalid type argument of
'->' (have 'int')
arch/alpha/include/asm/mmu_context.h:160:2: error: implicit declaratio
On Sat, 2017-09-16 at 11:20 -0700, Linus Torvalds wrote:
> On Fri, Sep 15, 2017 at 1:25 PM, Mimi Zohar wrote:
> >
> > To resolve this locking problem, this patch defines a new
> > ->integrity_read file operation method, which is equivalent to
> > ->read_iter, except that it will not take the i_rws
On Sat, Sep 16, 2017 at 06:26:04PM -0700, Randy Dunlap wrote:
> On 4.14-rc1, I am seeing lots of warnings on rcu kernel-doc:
>
> .. kernel-doc:: include/linux/rcupdate.h
>:external:
> ./Documentation/core-api/kernel-api.rst:357: ERROR: Error in "kernel-doc"
> directive:
> unknown option: "ext
A VAS window is normally in "busy" state for only a short duration.
Reduce the time we wait for the window to go to "not-busy" state to
speed-up vas_win_close() a bit.
Signed-off-by: Sukadev Bhattiprolu
---
arch/powerpc/platforms/powernv/vas-window.c | 10 ++
1 file changed, 6 insertions
Sanitize cpu/chip id to VAS id mapping, improve vas_win_close()
performance and add a check for return of credits.
Also, fix up couple of initializations/error checks and cleanup
some comments and debug code.
Sukadev Bhattiprolu (10):
powerpc/vas: init missing fields from [rt]xattr
powerpc/va
NX-842, the only user of VAS, sets the window credits to default values
but VAS should check the credits against the possible max values.
The VAS_WCREDS_MIN is not needed and can be dropped.
Signed-off-by: Sukadev Bhattiprolu
---
arch/powerpc/platforms/powernv/vas-window.c | 6 ++
arch/powe
Save the configured max window credits for a window in the vas_window
structure. We will need this when polling for return of window credits.
Signed-off-by: Sukadev Bhattiprolu
---
arch/powerpc/platforms/powernv/vas-window.c | 6 --
arch/powerpc/platforms/powernv/vas.h| 1 +
2 files
Use a helper to have the hardware unpin and mark a window closed.
Signed-off-by: Sukadev Bhattiprolu
---
arch/powerpc/platforms/powernv/vas-window.c | 22 +++---
1 file changed, 15 insertions(+), 7 deletions(-)
diff --git a/arch/powerpc/platforms/powernv/vas-window.c
b/arch/pow
Cleanuup vas.h and the debug code around ifdef vas_debug.
Signed-off-by: Sukadev Bhattiprolu
---
arch/powerpc/platforms/powernv/vas-window.c | 8 +++--
arch/powerpc/platforms/powernv/vas.h| 56 +++--
2 files changed, 18 insertions(+), 46 deletions(-)
diff --git
Create a cpu to vasid mapping so callers can specify -1 instead of
trying to find a VAS id.
Changelog[v2]
[Michael Ellerman] Use per-cpu variables to simplify code.
Signed-off-by: Sukadev Bhattiprolu
---
arch/powerpc/platforms/powernv/vas.c | 14 +-
1 file changed, 13 insert
Normally, the NX driver waits for the CRBs to be processed before closing
the window. But it is better to ensure that the credits are returned before
the window gets reassigned later.
Signed-off-by: Sukadev Bhattiprolu
---
arch/powerpc/platforms/powernv/vas-window.c | 45
Define a helper, chip_to_vas_id() to map a given chip id to corresponding
vas id.
Normally, callers of vas_rx_win_open() and vas_tx_win_open() would need
the VAS window to be on the same chip where the calling thread is executing.
These callers can pass in -1 for the VAS id.
This interface will b
Polling for window cast out is listed in the spec, but turns out that
it is not strictly necessary and slows down window close. Making it a
stub for now.
Signed-off-by: Sukadev Bhattiprolu
---
arch/powerpc/platforms/powernv/vas-window.c | 34 ++---
1 file changed, 17 inse
Initialize a few missing window context fields from the window attributes
specified by the caller. These fields are currently set to their default
values by the caller (NX-842), but would be good to apply them anyway.
Signed-off-by: Sukadev Bhattiprolu
---
arch/powerpc/platforms/powernv/vas-wind
On 09/14/2017 04:17 AM, Christophe LEROY wrote:
> Le 14/09/2017 à 01:51, Rob Landley a écrit :
>> From: Rob Landley
>>
>> Make initramfs honor CONFIG_DEVTMPFS_MOUNT, and move
>> /dev/console open after devtmpfs mount.
>>
>> Add workaround for Debian bug that was copied by Ubuntu.
>
> Is that a bu
On Tue, Aug 15, 2017 at 5:27 AM, Jan Kara wrote:
> On Mon 14-08-17 23:12:16, Dan Williams wrote:
>> The mmap syscall suffers from the ABI anti-pattern of not validating
>> unknown flags. However, proposals like MAP_SYNC and MAP_DIRECT need a
>> mechanism to define new behavior that is known to fai
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: 2bd6bf03f4c1c59381d62c61d03f6cc3fe71f66e
commit: 8073e960a03bf7b5d5ebfc5ff18ac475e1688f46 netfilter: nat: use keyed locks
date: 8 days ago
config: x86_64-randconfig-s4-09170918 (attached as .config)
compile
The current code mixes three distinct operations when transforming
the slave config to register settings:
1. special handling of DMA_SLAVE_BUSWIDTH_UNDEFINED, maxburst == 0
2. range checking
3. conversion of raw to register values
As the range checks depend on the specific SoC, move these o
The H3 supports bursts lengths of 1, 4, 8 and 16 transfers, each with
a width of 1, 2, 4 or 8 bytes.
The register value for the the width is log2-encoded, change the
conversion function to provide the correct value for width == 8.
Signed-off-by: Stefan Brüns
---
drivers/dma/sun6i-dma.c | 54 +++
Commit 3a03ea763a67 ("dmaengine: sun6i: Add support for Allwinner A83T
(sun8i) variant") and commit f008db8c00c1 ("dmaengine: sun6i: Add support for
Allwinner H3 (sun8i) variant") added support for the A83T resp. H3, but missed
some differences between the original A31 and A83T/H3.
The first patch
For the H3, the burst lengths field offsets in the channel configuration
register differs from earlier SoC generations.
Using the A31 register macros actually configured the H3 controller
do to bursts of length 1 always, which although working leads to higher
bus utilisation.
Signed-off-by: Stefa
The H83T uses a compatible string different from the A23, but requires
the same clock autogating register setting.
The H3 also requires setting the clock autogating register, but has
the register at a different offset.
Add three suitable callbacks for the existing controller generations
and set i
The A64 SoC has a DMA controller that supports 8 DMA channels
to and from various peripherals. The last used DRQ port is 27.
Add a device node for it.
Signed-off-by: Stefan Brüns
---
arch/arm64/boot/dts/allwinner/sun50i-a64.dtsi | 11 +++
1 file changed, 11 insertions(+)
diff --git a/a
Preparatory patch: If the same compatible is used for different SoCs which
have a common register layout, but different number of channels, the
channel count can no longer be stored in the config. Store it in the
device structure instead.
Signed-off-by: Stefan Brüns
---
drivers/dma/sun6i-dma.c |
The spi controller nodes omit the dma controller/channel references, add
it.
This does not yet enable DMA for SPI transfers, as the spi-sun6i driver
lacks support for DMA, but always uses PIO to the FIFO.
Signed-off-by: Stefan Brüns
---
arch/arm64/boot/dts/allwinner/sun50i-a64.dtsi | 4
1
To avoid introduction of a new compatible for each small SoC/DMA controller
variation, move the definition of the channel count to the devicetree.
The number of vchans is no longer explicit, but limited by the highest
port/DMA request number. The result is a slight overallocation for SoCs
with a s
The A64 SoC has the same dma engine as the H3 (sun8i), with a
reduced amount of physical channels. To allow future reuse of the
compatible, leave the channel count etc. in the config data blank
and retrieve it from the devicetree.
Signed-off-by: Stefan Brüns
---
drivers/dma/sun6i-dma.c | 23
The A64 is register compatible with the H3, but has a different number
of dma channels and request ports.
Attach additional properties to the node to allow future reuse of the
compatible for controllers with different number of channels/requests.
If dma-requests is not specified, the register lay
The lockdep code had reported the following unsafe locking scenario:
CPU0CPU1
lock(s_active#228);
lock(&bdev->bd_mutex/1);
lock(s_active#228);
lock(&bdev->bd_mutex);
*
On Sat, Sep 16, 2017 at 6:40 PM, kernel test robot
wrote:
>
> FYI, we noticed the following commit:
>
> commit: 7898f79654698dcea5a0876785796de67d527ee7 ("x86/mm/64: Fix an
> incorrect warning with CONFIG_DEBUG_VM=y, !PCID")
> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git master
Hi Icenowy,
On Tue, Sep 12, 2017 at 1:55 AM, Icenowy Zheng wrote:
> The DE2 CCU on Allwinner H5 SoC has a slightly different behavior than
> the one on H3, so the compatible string is not set in the common DTSI
> file.
>
> Add the compatible string of H5 DE2 CCU in H5 DTSI file.
>
> Signed-off-by
Hi Icenowy,
On Tue, Sep 12, 2017 at 1:55 AM, Icenowy Zheng wrote:
> The DE2 in H3/H5 has a clock control unit in it, and the behavior is
> slightly different between H3 and H5.
>
> Add the common parts in H3/H5 DTSI, and add the compatible string in H3
> DTSI.
>
> The compatible string of H5 DE2
Hi Felix,
FYI, the error/warning still remains.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: 2bd6bf03f4c1c59381d62c61d03f6cc3fe71f66e
commit: 70539bd79500245cbb4c7af00572fcce540d0105 drm/amd: Update MEC HQD
loading code for KFD
date: 5 weeks ago
co
FYI, we noticed the following commit:
commit: d830f6514cdf359bcd7201306ac792ffa27f7966 ("ipmi_si: Move platform
device handling to another file")
https://github.com/cminyard/linux-ipmi master-ipmi-rebase
in testcase: trinity
with following parameters:
runtime: 300s
test-description: T
FYI, we noticed the following commit:
commit: 89e689f267b2c144d7b071443e01fa718727b962 ("kernfs, sysfs, cgroup,
intel_rdt: Support fs_context")
https://git.kernel.org/cgit/linux/kernel/git/dhowells/linux-fs.git mount-context
in testcase: trinity
with following parameters:
runtime: 300s
FYI, we noticed the following commit:
commit: 7898f79654698dcea5a0876785796de67d527ee7 ("x86/mm/64: Fix an incorrect
warning with CONFIG_DEBUG_VM=y, !PCID")
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git master
in testcase: boot
on test machine: qemu-system-i386 -enable-kvm -c
scripts/kernel-doc handles DECLARE_BITMAP() and DECLARE_HASHTABLE().
Recently drivers/gpio/gpiolib.c has been changed to use DECLARE_KFIFO() *and*
that is inside kernel-doc notation, but scripts/kernel-doc doesn't know about
DECLARE_KFIFO(), so it causes these warnings:
../drivers/gpio/gpiolib.c:
On 4.14-rc1, I am seeing lots of warnings on rcu kernel-doc:
.. kernel-doc:: include/linux/rcupdate.h
:external:
./Documentation/core-api/kernel-api.rst:357: ERROR: Error in "kernel-doc"
directive:
unknown option: "external".
.. kernel-doc:: include/linux/rcupdate_wait.h
:external:
./Docum
On Fri, Sep 15, 2017 at 04:44:38PM +0530, Neeraj Upadhyay wrote:
> Hi,
>
> We have one query regarding the behavior of RCU expedited grace period,
> for scenario where resched_cpu() in sync_sched_exp_handler() fails to
> acquire the rq lock and returns w/o setting the need_resched. In this
> case,
Yes, I realize this is a day early, and yes, I realize that if I had
waited until tomorrow, I would also have hit the 26th anniversary of
the Linux-0.01 release, but neither of those undeniable facts made me
want to wait with closing the mege window.
This has been an "interesting" merge window. It
On 09/15/2017 10:37 AM, Christoph Hellwig wrote:
On Fri, Sep 15, 2017 at 09:54:08AM -0700, Laura Abbott wrote:
Hi,
Fedora got a bug report on an early version of 4.13.2
https://paste.fedoraproject.org/paste/t-Yx23LN5QwJ7oPZLj3zrg
Can you check if the issue goes away when you disable
CONFIG_VI
Hi Marc,
On 09/16/2017 01:14 PM, Marc Zyngier wrote:
> On Fri, Sep 15 2017 at 10:08:56 am BST, Shanker Donthineni
> wrote:
>
> Hi Shanker,
>
>> A new feature Range Selector (RS) has been added to GIC specification
>> in order to support more than 16 CPUs at affinity level 0. New fields
>> are
On Sat, 16 Sep 2017 15:22:23 -0700
Jonathan Cameron wrote:
> On Thu, 14 Sep 2017 16:31:06 +0200
> Michael Hennerich wrote:
>
> > On 14.09.2017 15:50, Stefan Popa wrote:
> > > SPI host drivers can use DMA to transfer data, so the buffer should be
> > > properly allocated.
> > > Keeping it on
On Thu, 14 Sep 2017 16:31:06 +0200
Michael Hennerich wrote:
> On 14.09.2017 15:50, Stefan Popa wrote:
> > SPI host drivers can use DMA to transfer data, so the buffer should be
> > properly allocated.
> > Keeping it on the stack could cause an undefined behavior.
> >
> > The dedicated reset fun
On 09/16/2017 02:29 AM, Josh Poimboeuf wrote:
> On Fri, Sep 15, 2017 at 11:01:19AM -0700, Linus Torvalds wrote:
>> On Fri, Sep 15, 2017 at 9:53 AM, Andrey Ryabinin
>> wrote:
>>>
>>> I'm not so sure that this is disabled optimization. I assume that global
>>> rsp makes
>>> changes something in gcc
On Thu, 14 Sep 2017 23:19:22 +0200
Paolo Cretaro wrote:
> Fix gcc warning:
> cros_ec_baro.c:130:25: warning: variable ‘ec_device’ set but not used
>
> Signed-off-by: Paolo Cretaro
Applied to the togreg branch of iio.git and pushed out as testing for
the autobuilders to play with it.
Thanks,
On Sat, 16 Sep 2017 12:05:49 +0200
Quentin Schulz wrote:
> Hi Icenowy,
>
> On 14/09/2017 16:52, Icenowy Zheng wrote:
> > Because of the restriction of the OF thermal framework, the thermal
> > sensor will fail to probe if the thermal zone doesn't exist.
> >
>
> Oh no, that's not good.
>
> W
On Sat, 16 Sep 2017 11:45:47 +0200
Quentin Schulz wrote:
> Hi Icenowy,
>
> On 14/09/2017 16:52, Icenowy Zheng wrote:
> > This adds support for the Allwinner H3 thermal sensor.
> >
> > Allwinner H3 has a thermal sensor like the one in A33, but have its
> > registers nearly all re-arranged, sampl
On Thu, 14 Sep 2017 22:52:46 +0800
Icenowy Zheng wrote:
> Allwinner H3 features a thermal sensor like the one in A33, but has its
> register re-arranged, the clock divider moved to CCU (originally the
> clock divider is in ADC) and added a pair of bus clock and reset.
>
> Update the binding docu
On Sat, Sep 16, 2017 at 2:47 PM, Thomas Gleixner wrote:
>
> Yes and no. We get more code which uses cpumasks to store state, just like
> I did, and while a lot of the cpumask functions just work as expected a
> subset including for_each_cpu does not. That's confusing at best and I
> rather avoid t
On Sat, 16 Sep 2017, Linus Torvalds wrote:
> On Sat, Sep 16, 2017 at 11:12 AM, Thomas Gleixner wrote:
> >>
> >> So I suspect your perf fix is the right one, and maybe we could/should
> >> just make people more aware of the empty cpumask issue with UP.
> >
> > Right, I just got a bit frightened as
On 09/16/2017 06:28 AM, Daniel Lezcano wrote:
On 16/09/2017 08:23, Dmitriy Cherkasov wrote:
On 09/13/2017 11:15 AM, Daniel Lezcano wrote:
Where is get_cycles64() ?
This is in asm/timex.h. Should this be split into a separate asm header
ala arm64?
No, it is fine but may be it is get_cycle
The probe function calls omap_gpio_show_rev(), which on most
compilers is inlined, but on the old gcc-4.6 is not, causing
a valid warning about the incorrect __init annotation:
WARNING: vmlinux.o(.text+0x40f614): Section mismatch in reference from the
function omap_gpio_probe() to the function .i
The new isofs_show_options() function fails to build when CONFIG_NLS
is disabled:
fs/isofs/inode.c: In function 'isofs_show_options':
fs/isofs/inode.c:518:44: error: 'CONFIG_NLS_DEFAULT' undeclared (first use in
this function)
fs/isofs/inode.c:518:44: note: each undeclared identifier is reported
This reverts commit 36ae3c0a36b7456432fedce38ae2f7bd3e01a563.
The commit broke compilation on !CONFIG_HAVE_KVM_IRQ_ROUTING. Also,
there may be cases with CONFIG_HAVE_KVM_IRQ_ROUTING, where larger
gsi values make sense.
As the commit was meant as an early indicator to user space that
something is
From: Markus Elfring
Date: Sat, 16 Sep 2017 21:38:03 +0200
Replace the specification of data structures by variable references
as the parameter for the operator "sizeof" to make the corresponding size
determination a bit safer according to the Linux coding style convention.
Signed-off-by: Markus
From: Markus Elfring
Date: Sat, 16 Sep 2017 21:24:27 +0200
* Omit an extra message for a memory allocation failure in this function.
This issue was detected by using the Coccinelle software.
* Add a jump target so that the function "kfree" will be always called
with a non-null pointer.
Sig
From: Markus Elfring
Date: Sat, 16 Sep 2017 21:48:45 +0200
Two update suggestions were taken into account
from static source code analysis.
Markus Elfring (2):
Delete an error message for a failed memory allocation
Improve three size determinations
drivers/media/tuners/m88rs6000t.c | 13 ++
On Sat, 2017-09-16 at 12:33 +0100, Colin King wrote:
> From: Colin Ian King
>
> The structure stm32f7_setup is local to the source and does not need
> to be in global scope, so make it static.
>
> Cleans up sparse warning:
> symbol 'stm32f7_setup' was not declared. Should it be static?
[]
> diff
Linus,
The following changes since commit 569dbb88e80deb68974ef6fdd6a13edb9d686261:
Linux 4.13 (2017-09-03 13:56:17 -0700)
are available in the git repository at:
git://git.infradead.org/linux-ubifs.git tags/upstream-4.14-rc1
for you to fetch changes up to 89b68cd926633ff0df1e1a0ae29fcd80f
Linus,
The following changes since commit 569dbb88e80deb68974ef6fdd6a13edb9d686261:
Linux 4.13 (2017-09-03 13:56:17 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/rw/uml.git for-linus-4.14-rc1
for you to fetch changes up to 6d20e6b235aad0be463b
nvm_tgt_types list was protected by wrong lock for NVM_INFO ioctl call
and can race with addition or removal of target types. Also
unregistering target type was not protected correctly.
Fixes: 5cd907853 ("lightnvm: remove nested lock conflict with mm")
Signed-off-by: Rakesh Pandit
---
V2: also
From: Suniel Mahesh
ti-cpufreq.c and cpufreq-dt-platdev.c are registering
platform device with same name "cpufreq-dt" using
platform_device_register_*() routines.
This is leading to build warnings appended below.
This patch does the following:
(a) Remove platform-device registration routine from
From: Markus Elfring
Date: Sat, 16 Sep 2017 20:06:01 +0200
Replace the specification of data structures by variable references
as the parameter for the operator "sizeof" to make the corresponding size
determination a bit safer according to the Linux coding style convention.
Signed-off-by: Markus
From: Markus Elfring
Date: Sat, 16 Sep 2017 19:40:47 +0200
* Omit extra messages for a memory allocation failure in this function.
This issue was detected by using the Coccinelle software.
* Delete the label "err" and the variable "ret" which became unnecessary
with this refactoring.
Signe
Commit-ID: 9cb067ef8a10bb13112e4d1c0ea996ec96527422
Gitweb: http://git.kernel.org/tip/9cb067ef8a10bb13112e4d1c0ea996ec96527422
Author: Thomas Gleixner
AuthorDate: Wed, 13 Sep 2017 23:29:03 +0200
Committer: Thomas Gleixner
CommitDate: Sat, 16 Sep 2017 20:20:56 +0200
genirq: Fix cpumask
From: Markus Elfring
Date: Sat, 16 Sep 2017 20:12:34 +0200
Two update suggestions were taken into account
from static source code analysis.
Markus Elfring (2):
Delete two error messages for a failed memory allocation
Improve three size determinations
drivers/media/tuners/it913x.c | 3 +--
On Sat, Sep 16, 2017 at 11:12 AM, Thomas Gleixner wrote:
>>
>> So I suspect your perf fix is the right one, and maybe we could/should
>> just make people more aware of the empty cpumask issue with UP.
>
> Right, I just got a bit frightened as I really was not aware about that
> 'opmtimization' whi
On Fri, Sep 15, 2017 at 1:25 PM, Mimi Zohar wrote:
>
> To resolve this locking problem, this patch defines a new
> ->integrity_read file operation method, which is equivalent to
> ->read_iter, except that it will not take the i_rwsem lock, but will
> be called with the i_rwsem held exclusively.
>
I've got this kmemleak splat
unreferenced object 0x880f687ff6a8 (size 32):
comm "cp", pid 4279, jiffies 4295784487 (age 2866.296s)
hex dump (first 32 bytes):
01 00 00 02 02 00 08 00 00 00 00 00 00 00 00 00
00 00 00 00 00 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b a5 .kkk
On Fri, Sep 15 2017 at 10:08:56 am BST, Shanker Donthineni
wrote:
Hi Shanker,
> A new feature Range Selector (RS) has been added to GIC specification
> in order to support more than 16 CPUs at affinity level 0. New fields
> are introduced in SGI system registers (ICC_SGI0R_EL1, ICC_SGI1R_EL1
>
On Sat, 16 Sep 2017, Linus Torvalds wrote:
> On Sat, Sep 16, 2017 at 10:35 AM, Thomas Gleixner wrote:
> >
> > Don't bother. I found it already. On UP we have:
> >
> > #define for_each_cpu(cpu, mask) \
> > for ((cpu) = 0; (cpu) < 1; (cpu)++, (void)mask)
> >
> > which is a tota
Loan Offer at 3%, Feel Free to REPLY back to us for more info.
nvm_tgt_types list was protected by wrong lock for NVM_INFO ioctl call
and can race with addition or removal of target types.
Fixes: cd9e9808d ("lightnvm: Support for Open-Channel SSDs")
Signed-off-by: Rakesh Pandit
---
drivers/lightnvm/core.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletio
On Sat, Sep 16, 2017 at 10:53 AM, Greg K-H wrote:
>
> Ah doh, you are so right, sorry about that. I'm getting onto a flight right
> now but will send this on to Linus when I land in the morning.
I'll take it directly, I'm planning on closing the merge window today anyway.
Linus
On Sat, Sep 16, 2017 at 10:35 AM, Thomas Gleixner wrote:
>
> Don't bother. I found it already. On UP we have:
>
> #define for_each_cpu(cpu, mask) \
> for ((cpu) = 0; (cpu) < 1; (cpu)++, (void)mask)
>
> which is a total fail as it breaks any code which uses for_each_cpu() or
>
On September 16, 2017 10:20:51 AM PDT, Markus Trippelsdorf
wrote:
>On 2017.09.16 at 09:55 -0700, Greg KH wrote:
>> On Sat, Sep 16, 2017 at 08:25:03AM +0200, Markus Trippelsdorf wrote:
>> > On 2017.09.16 at 06:51 +0200, Markus Trippelsdorf wrote:
>> > > On 2017.09.15 at 11:56 -0700, Greg KH wrote:
On 09/15/17 15:42, Rob Herring wrote:
> On Fri, Sep 15, 2017 at 5:16 PM, wrote:
>> From: Frank Rowand
>
> I feel like we just had the same subject. Can you make it more specific.
Yes, the previous one was pretty much the same words, but the one line
description is not an exact match. I will c
On 09/16/2017 06:24 PM, Abdul Haleem wrote:
> Hi,
>
> Today's mainline kernel failed to build on powerpc with below error
>
> arch/powerpc/kvm/../../../virt/kvm/eventfd.c: In function ‘kvm_irqfd’:
> arch/powerpc/kvm/../../../virt/kvm/eventfd.c:568:19: error:
> ‘KVM_MAX_IRQ_ROUTES’ undeclared (fi
On Sat, 16 Sep 2017, Fengguang Wu wrote:
> > > [0.038086] Performance Events: unsupported p6 CPU model 61 no PMU
> > > driver, software events only.
>
> What's your host CPU? I can reproduce it in Nehalem, Haswell and Sandy
> Bridge machines with the attached script.
My bad. I booted the wron
On 09/16/2017 06:27 AM, Zwindl wrote:
Hi, I've done the test, and the weird thing happened. The kernel buit with this
config file https://ptpb.pw/HF1g which is from
https://aur.archlinux.org/packages/linux-git/ can run properly, the wifi can
connect, despite which version it is, but, with this
On 2017.09.16 at 09:55 -0700, Greg KH wrote:
> On Sat, Sep 16, 2017 at 08:25:03AM +0200, Markus Trippelsdorf wrote:
> > On 2017.09.16 at 06:51 +0200, Markus Trippelsdorf wrote:
> > > On 2017.09.15 at 11:56 -0700, Greg KH wrote:
> > > > The following changes since commit
> > > > 569dbb88e80deb68974
On Sat, 16 Sep 2017, Srishti Sharma wrote:
> Eliminate the fields that are not used and the comments
> associated with them.
>
> Signed-off-by: Srishti Sharma
Acked-by: Julia Lawall
> ---
> Changes in v2:
> - Use the word field instead of variable.
>
> drivers/staging/dgnc/dgnc_driver.h |
On Sat, 16 Sep 2017, Srishti Sharma wrote:
> Remove unused fields and comments associated with them in
> the structure definition.
>
> Signed-off-by: Srishti Sharma
Acked-by: Julia Lawall
> ---
> Changes in v2:
> - Use the word field instead of variable.
>
> drivers/staging/dgnc/dgnc_drive
On Sat, Sep 16, 2017 at 11:01:16AM +0200, Markus Trippelsdorf wrote:
> Commit 5620a0d1aac ("firmware: delete in-kernel firmware") removed the
> entire firmware directory. Unfortunately it thereby also removed the
> support for built-in firmware.
The goal was to delete the in-kernel firmware, why d
On Sat, Sep 16, 2017 at 08:25:03AM +0200, Markus Trippelsdorf wrote:
> On 2017.09.16 at 06:51 +0200, Markus Trippelsdorf wrote:
> > On 2017.09.15 at 11:56 -0700, Greg KH wrote:
> > > The following changes since commit
> > > 569dbb88e80deb68974ef6fdd6a13edb9d686261:
> > >
> > > Linux 4.13 (2017-0
From: Colin Ian King
txbuf16 is being initialized at declaration time and then later
set to another value without it being read inbetween, hence making
the initialization redundant. Fix this by setting txbuf16 just
the once. Also clean up some incorrect indentations. Cleans up
clang build warnin
Eliminate the fields that are not used and the comments
associated with them.
Signed-off-by: Srishti Sharma
---
Changes in v2:
- Use the word field instead of variable.
drivers/staging/dgnc/dgnc_driver.h | 6 --
1 file changed, 6 deletions(-)
diff --git a/drivers/staging/dgnc/dgnc_driver.
Remove unused fields and comments associated with them in
the structure definition.
Signed-off-by: Srishti Sharma
---
Changes in v2:
- Use the word field instead of variable.
drivers/staging/dgnc/dgnc_driver.h | 9 -
1 file changed, 9 deletions(-)
diff --git a/drivers/staging/dgnc/dgn
Remove fields that are not used, from structure definitions , and
eliminate the comments associated with them.
Srishti Sharma (2):
Staging: dgnc: Remove unused variables in structure definition
Staging: dgnc: Remove unused variable in structure
drivers/staging/dgnc/dgnc_driver.h | 15 --
From: Colin Ian King
Variable idx is being set but never read and thus it can be
removed because it is redundant. Cleans up clang build warnings:
warning: Value stored to 'idx' during its initialization is never read
warning: Value stored to 'idx' is never read
warning: Value stored to 'idx' is
1) Fix hotplug deadlock in hv_netvsc, from Stephen Hemminger.
2) Fix double-free in rmnet driver, from Dan Carpenter.
3) INET connection socket layer can double put request sockets,
fix from Eric Dumazet.
4) Don't match collect metadata-mode tunnels if the device is down,
from Haishuang Y
1 - 100 of 208 matches
Mail list logo
