On 2017/12/14 15:42, Greg KH wrote:
On Thu, Dec 14, 2017 at 11:39:36AM +0800, Jason Yan wrote:
Some driviers may have the chance to increase a reference count that
has dropped to zero when using get_device() because of their design.
Then those drivers are broken :)
We have met such a issue w
On Tue, Dec 12, 2017 at 06:47:33PM -0800, Guenter Roeck wrote:
> On 12/12/2017 04:43 AM, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 4.14.6 release.
> > There are 164 patches in this series, all will be posted as a response
> > to this one. If anyone has any
On Tue, Dec 12, 2017 at 05:30:42PM -0700, Nathan Chancellor wrote:
> On Tue, Dec 12, 2017 at 04:22:36PM -0800, Guenter Roeck wrote:
> > On 12/12/2017 04:43 AM, Greg Kroah-Hartman wrote:
> > > This is the start of the stable review cycle for the 4.9.69 release.
> > > There are 148 patches in this se
On Wed, Dec 13, 2017 at 05:28:44PM +0530, Naresh Kamboju wrote:
> On 12 December 2017 at 18:13, Greg Kroah-Hartman
> wrote:
> > This is the start of the stable review cycle for the 4.9.69 release.
> > There are 148 patches in this series, all will be posted as a response
> > to this one. If anyon
On Wed, Dec 13, 2017 at 01:23:38PM -0800, Stephen Hemminger wrote:
> On Wed, 13 Dec 2017 09:54:19 +0100
> Vincent Legoll wrote:
>
> > Hello,
> >
> > On Sun, Dec 10, 2017 at 6:50 AM, Stephen Hemminger
> > wrote:
> > > Will this break existing configs?
> >
> > I don't think so. Last time I did
On Wed 13-12-17 16:45:55, Mike Kravetz wrote:
> On 12/04/2017 06:01 AM, Michal Hocko wrote:
> > From: Michal Hocko
> >
> > alloc_surplus_huge_page increases the pool size and the number of
> > surplus pages opportunistically to prevent from races with the pool size
> > change. See d1c3fb1f8f29 ("
Added the basic driver for Arasan NAND Flash Controller used in
Zynq UltraScale+ MPSoC. It supports only Hw ECC and upto 24bit
correction.
Signed-off-by: Naga Sureshkumar Relli
Signed-off-by: Punnaiah Choudary Kalluri
---
Changes in v8:
- Implemented setup_data_interface hook
- fixed checkpatc
This patch series adds the basic driver support for Arasan NAND Flash
controller.
We are reinitiating the patch series by fixing the comments given by
Boris and Rob.
Previous Patch reference:
https://lkml.org/lkml/2017/1/8/245
Naga Sureshkumar Relli (2):
mtd: arasan: Add device tree binding doc
This patch adds the dts binding document for arasan nand flash
controller.
Signed-off-by: Naga Sureshkumar Relli
Signed-off-by: Punnaiah Choudary Kalluri
---
Changes in v8:
- Updated compatible and clock-names as per Boris comments
Changes in v7:
- Corrected the acronyms those should be in caps
On Wed, Dec 13, 2017 at 6:07 AM, Greg Kroah-Hartman
wrote:
> On Wed, Dec 13, 2017 at 05:16:13PM +0530, Aniruddha Shastri wrote:
>> On Wed, Dec 13, 2017 at 4:20 PM, Greg Kroah-Hartman
>> wrote:
>> >
>> > On Wed, Dec 13, 2017 at 04:01:04AM -0600, Aniruddha Shastri wrote:
>> > > Fix checkpatch warni
On Thu, Dec 14, 2017 at 11:39:36AM +0800, Jason Yan wrote:
> Some driviers may have the chance to increase a reference count that
> has dropped to zero when using get_device() because of their design.
Then those drivers are broken :)
> We have met such a issue with scsi:
> https://www.spinics.net
On Thu, 2017-12-14 at 13:13 +0800, kbuild test robot wrote:
> Hi Ching,
>
> Thank you for the patch! Perhaps something to improve:
>
> [auto build test WARNING on scsi/for-next]
> [also build test WARNING on next-20171213]
> [cannot apply to v4.15-rc3]
> [if your patch
On Wed 13-12-17 15:35:33, Mike Kravetz wrote:
> On 12/04/2017 06:01 AM, Michal Hocko wrote:
[...]
> > Before migration
> > /sys/devices/system/node/node0/hugepages/hugepages-2048kB/free_hugepages:0
> > /sys/devices/system/node/node0/hugepages/hugepages-2048kB/nr_hugepages:1
> > /sys/devices/system/
On Thu, Dec 14, 2017 at 11:19:31AM +0530, Vinod Koul wrote:
> Changes in v6:
> - Add reviewed/acked tags from Philippe, Pierre, Takashi and Greg
> - Fix nitpicks from Takashi
> - Drop the sysfs patch for now
Wait, why drop the sysfs patch entirely? You need those attributes,
right? You als
Am 13.12.2017 um 21:51 schrieb Tomas Marek:
This patch fix brace on next line coding style errors reported by
checkpatch.
Signed-off-by: Tomas Marek
Acked-by: Stefan Wahren
Thanks
Two of these warnings are now line-too-long warnings. I think these
warnings are preferable to the ones listed below. The longest line is
only 85 chars wide, which is reasonable.
Warnings fixed:
ni_atmio.c:239: WARNING: Avoid multiple line dereference
- prefer 'ni_boards[i].isapnp_id'
ni_
On 30-11-17, 12:29, Viresh Kumar wrote:
> On 29-11-17, 16:50, Stephen Boyd wrote:
> > Sorry it still makes zero sense to me. It seems that we're trying
> > to make the OPP table parsing generic just for the sake of code
> > brevity.
>
> Not just the code but bindings as well to make sure we don't
On Wed, Dec 13, 2017 at 11:31:15AM -0800, Tomas Marek wrote:
> On 12/13/2017 03:55 AM, Greg KH wrote:
>
> > On Sat, Dec 09, 2017 at 12:41:11PM -0800, Tomas Marek wrote:
> >> This patch fix several brace on next line, braces not necessary, space
> >> around =/<, and space before/after open/close pa
On Thu 14-12-17 09:40:32, kemi wrote:
>
>
> On 2017年12月12日 16:11, Michal Hocko wrote:
> > On Tue 12-12-17 10:05:26, kemi wrote:
> >>
> >>
> >> On 2017年12月08日 16:47, Michal Hocko wrote:
> >>> On Fri 08-12-17 16:38:46, kemi wrote:
>
>
> On 2017年11月30日 17:45, Michal Hocko wrote:
> >>>
When any of the DAI hardware configuration callbacks (.hw_param,
.set_fmt, .set_sysclk) fails, there is no explanation about why it
failed. This is particularly confusing for .hw_param, which covers
many parameters of the DAI. Telling the users what parameter isn't
supported, and what the requested
On Thu, Dec 14, 2017 at 11:51:17AM +0530, Aishwarya Pant wrote:
> On Wed, Dec 13, 2017 at 12:50:00PM +0100, Greg Kroah-Hartman wrote:
> > On Mon, Dec 11, 2017 at 03:24:30PM +0530, Aishwarya Pant wrote:
> > > This is a clean-up patch which replaces the uses of raw __ATTR(...)
> > > macro with the mo
On Thu, Dec 14, 2017 at 05:00:33PM +1100, Stephen Rothwell wrote:
> Hi Greg,
>
> After merging the staging.current tree, today's linux-next build (powerpc
> allyesconfig) failed like this:
>
> drivers/staging/android/ion/ion_cma_heap.c: In function 'ion_cma_allocate':
> drivers/staging/android/io
On Wed, Dec 13, 2017 at 01:26:04PM -0800, John Stultz wrote:
> In trying to add support for drm_hwcomposer to HiKey,
> I've needed to utilize the ION CMA heap, and I've noticed
> problems with allocations on newer kernels failing.
>
> It seems back with 204f672255c2 ("ion: Use CMA APIs directly"),
On Wed, Dec 13, 2017 at 01:26:04PM -0800, John Stultz wrote:
> In trying to add support for drm_hwcomposer to HiKey,
> I've needed to utilize the ION CMA heap, and I've noticed
> problems with allocations on newer kernels failing.
>
> It seems back with 204f672255c2 ("ion: Use CMA APIs directly"),
Hi,
In function __ext4_grp_locked_error, __save_error_info(sb, function, line)
is called to save error info in super block block, but does not sync
that information
to disk to info the subsequence fsck after reboot. The reason, I guess
maybe it is
in locked state.
My question is why not m
On Wed 13-12-17 15:19:00, Kees Cook wrote:
> On Wed, Dec 13, 2017 at 6:40 AM, Cyril Hrubis wrote:
> > Hi!
> >> You selected stupid name for a flag. Everyone and their dog agrees
> >> with that. There's even consensus on better name (and everyone agrees
> >> it is better than .._SAFE). Of course, w
Hi all,
Changes since 20171213:
The staging.current tree gained a build failure for which I reverted
a commit.
The clk tree lost its build failures.
The bpf-next tree lost its build failure.
The drm tree gained a conflict against the drm-misc-fixes tree.
Non-merge commits (relative to Linus
On Thu, Dec 07, 2017 at 04:58:45PM +0100, Maxime Ripard wrote:
> Hi,
>
> Here is an attempt at supporting the LVDS output in our DRM driver. This
> has been tested on the A83T (with DE2), but since everything is basically
> in the TCON, it should also be usable on the older SoCs with minor
> modif
On Thu, 2017-12-14 at 00:27 -0600, Aniruddha Shastri wrote:
> Three of these warnings are now line-too-long warnings. I think these
> warnings are preferable to the ones listed below. The longest line
> is only 87 chars wide, which is reasonable.
[]
> diff --git a/drivers/staging/comedi/drivers/n
On Wed, 13 Dec 2017 13:57:45 -0500
Josef Bacik wrote:
> On Wed, Dec 13, 2017 at 10:07:32AM -0800, Darrick J. Wong wrote:
> > On Wed, Dec 13, 2017 at 01:03:57PM -0500, Josef Bacik wrote:
> > > On Tue, Dec 12, 2017 at 03:11:50PM -0800, Darrick J. Wong wrote:
> > > > On Mon, Dec 11, 2017 at 11:36:45
On 2017年12月13日 20:20, Paolo Bonzini wrote:
> On 13/12/2017 05:17, Lan Tianyu wrote:
>> Reported by syzkaller:
>> WARNING: CPU: 0 PID: 27962 at arch/x86/kvm/emulate.c:5631
>> x86_emulate_insn+0x557/0x15f0 [kvm]
>> Modules linked in: kvm_intel kvm [last unloaded: kvm]
>> CPU: 0 PID: 2796
Hi, Dave,
Dave Hansen writes:
> On 12/13/2017 07:38 PM, Lu Baolu wrote:
>> 2. When vmalloc/vfree interfaces are called, the page mappings
>> for kernel memory might get changed. And current code calls
>> flush_tlb_kernel_range() to flush CPU TLBs only. The IOTLB or
>> DevTLB will be
Three of these warnings are now line-too-long warnings. I think these
warnings are preferable to the ones listed below. The longest line
is only 87 chars wide, which is reasonable.
Warnings fixed:
ni_670x.c:212: WARNING: struct comedi_lrange should normally be const
ni_atmio.c:239: WARNING: Avoi
Replace the original license statement with the SPDX identifier.
Signed-off-by: Andi Shyti
Reviewed-by: Krzysztof Kozlowski
---
Hi,
v2 to v3:
- move the SPDX identifier on top as a separate comment as per
documentation
- add Krzysztof's review
v1 to v2:
- keep the original license
Andi
On 12/13/2017 07:38 PM, Lu Baolu wrote:
> 2. When vmalloc/vfree interfaces are called, the page mappings
> for kernel memory might get changed. And current code calls
> flush_tlb_kernel_range() to flush CPU TLBs only. The IOTLB or
> DevTLB will be stale compared to that on the cpu for k
On Wed, Dec 13, 2017 at 12:50:00PM +0100, Greg Kroah-Hartman wrote:
> On Mon, Dec 11, 2017 at 03:24:30PM +0530, Aishwarya Pant wrote:
> > This is a clean-up patch which replaces the uses of raw __ATTR(...)
> > macro with the more conventional DEVICE_ATTR(...) for defining device
> > attributes.
> >
On 12/13/2017 05:40 PM, Maxime Ripard wrote:
Hi,
On Wed, Dec 13, 2017 at 09:44:34AM +0200, Stefan Mavrodiev wrote:
Allwinner A10/A13/A20 SoCs have pinmux for spi0
on port C. The patch adds these pins in the respective
dts includes.
Signed-off-by: Stefan Mavrodiev
Do you have any boards that
Andi,
On Thu, Dec 14, 2017 at 2:31 AM, Andi Shyti wrote:
> Hi Philippe,
>
>> > diff --git a/include/linux/platform_data/spi-s3c64xx.h
>> > b/include/linux/platform_data/spi-s3c64xx.h
>> > index da79774078a7..8917f38c97c5 100644
>> > --- a/include/linux/platform_data/spi-s3c64xx.h
>> > +++ b/incl
If 'mtd_device_parse_register()' fails, we still return 0 which mean
success.
Return the error code instead, as done in all the other error handling
paths.
Signed-off-by: Christophe JAILLET
---
Cross-compiled tested-only
v2: call 'onenand_release()' to undo 'onenand_scan()'
v3: no change
---
dr
This include is not needed, so remove it.
Signed-off-by: Christophe JAILLET
---
Cross-compiled tested-only
v3: new patch in the serie
---
drivers/mtd/onenand/samsung.c | 2 --
1 file changed, 2 deletions(-)
diff --git a/drivers/mtd/onenand/samsung.c b/drivers/mtd/onenand/samsung.c
index 206aa9
On 2017/12/14 11:38, Lu Baolu wrote:
> Hi,
>
> On 12/14/2017 11:10 AM, Bob Liu wrote:
>> On 2017/12/14 9:02, Lu Baolu wrote:
From: Huang Ying
Shared Virtual Memory (SVM) allows a kernel memory mapping to be
shared between CPU and and a device which requested a supervisor
Hi Jens,
do you think this version could be ok?
Thanks,
Paolo
> Il giorno 04 dic 2017, alle ore 11:42, Paolo Valente
> ha scritto:
>
> Commit a33801e8b473 ("block, bfq: move debug blkio stats behind
> CONFIG_DEBUG_BLK_CGROUP") introduced two batches of confusing ifdefs:
> one reported in [1],
Propagate the error code returned by 'onenand_scan()' instead of a
hard-coded -EFAULT.
Signed-off-by: Christophe JAILLET
---
Cross-compiled tested-only
v3: new patch in the serie
---
drivers/mtd/onenand/samsung.c | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/drivers/m
Convert all error handling code in 's3c_onenand_probe()' to
resource-managed alternatives in order to simplify code.
This fixes a resource leak if 'platform_get_resource()' fails at line 872.
The 'request_irq()' at line 971 was also un-balanced. It is now
resource-managed.
Signed-off-by: Christo
The first patch converts 's3c_onenand_probe()' to devm_ functions.
This fixes a leak in one path (line 872).
This also free_irq which was not handled at all. ( I hope I'm correct :) )
The 2nd patch is about an un-handled error code which looks spurious.
Not sure if I'm right.
The 3rd patch propag
Hi Greg,
After merging the staging.current tree, today's linux-next build (powerpc
allyesconfig) failed like this:
drivers/staging/android/ion/ion_cma_heap.c: In function 'ion_cma_allocate':
drivers/staging/android/ion/ion_cma_heap.c:38:14: error: 'CONFIG_CMA_ALIGNMENT'
undeclared (first use in
On Thu, Dec 14, 2017 at 12:07 PM, Theodore Ts'o wrote:
> On Wed, Dec 13, 2017 at 04:13:07PM +0900, Byungchul Park wrote:
>>
>> Therefore, I want to say the fundamental problem
>> comes from classification, not cross-release
>> specific.
>
> You keep saying that it is "just" a matter of classificai
Xilinx ZYNQMP logicoreIP Init driver is based on the new
LogiCoreIP design created. This driver provides the processing system
and programmable logic isolation. Set the frequency based on the clock
information get from the logicoreIP register set.
It is put in drivers/misc as there is no subsystem
Add Device Tree binding document for logicoreIP. This logicoreIP
provides the isolation between the processing system and
programmable logic. Also provides the clock related information.
Signed-off-by: Dhaval Shah
---
Chnages since v3:
* Use "dt-bindings: misc: ..." for the subject.
Changes sinc
1st patch provide Device Tree binding document for logicoreIP
2nd patch provide the xlnx_vcu logicoreIP driver, Kconfig changes
and Makefile changes for the driver.
Dhaval Shah (2):
Documentation: devicetree: Add DT bindings to xlnx_vcu driver
misc: Add Xilinx ZYNQMP VCU logicoreIP init driver
On Tue, Dec 12, 2017 at 04:45:14PM -0800, Luis R. Rodriguez wrote:
> Modern gdbm-devel packages bundle together gdbm.h and ndbm.h.
> The old m4 macro had detection support for some old gdbm libraries
> but not for new ones.
>
> We fix compilation of src/dbtest.c by making the autoconf helper
> che
On 2017-12-14 03:53, Stephen Boyd wrote:
On 12/11, Abhishek Sahu wrote:
On 2017-12-09 05:46, Stephen Boyd wrote:
>On 12/08, Abhishek Sahu wrote:
>>On 2017-12-07 11:53, Stephen Boyd wrote:
>>>On 09/28, Abhishek Sahu wrote:
This patch series does the miscellaneous changes in QCOM Alpha PLL
>>>
This adds the base SoundWire bus type, bus and driver registration.
along with changes to module device table for new SoundWire
device type.
Signed-off-by: Sanyog Kale
Reviewed-by: Philippe Ombredanne
Acked-By: Pierre-Louis Bossart
Reviewed-by: Takashi Iwai
Acked-by: Greg Kroah-Hartman
Signed
SoundWire bus provides sdw_read() and sdw_write() APIs for Slave
devices to program the registers. Provide support in regmap for
SoundWire bus.
Signed-off-by: Hardik T Shah
Signed-off-by: Sanyog Kale
Reviewed-by: Philippe Ombredanne
Acked-By: Pierre-Louis Bossart
Reviewed-by: Takashi Iwai
Sig
A Master adds a SoundWire bus instance which scans the firmware
provided for device description.
In this patch we scan ACPI namespaces and create SoundWire
Slave devices based on ACPI description
Signed-off-by: Sanyog Kale
Reviewed-by: Philippe Ombredanne
Acked-By: Pierre-Louis Bossart
Reviewe
Add status handling API sdw_handle_slave_status() to handle
Slave status changes.
Signed-off-by: Hardik T Shah
Signed-off-by: Sanyog Kale
Reviewed-by: Philippe Ombredanne
Acked-By: Pierre-Louis Bossart
Reviewed-by: Takashi Iwai
Signed-off-by: Vinod Koul
---
drivers/soundwire/bus.c | 3
The SoundWire Master is implemented as part of Audio controller in
Intel platforms. Add a init module which creates SoundWire Master
platform devices based on the links supported in the hardware.
Signed-off-by: Sanyog Kale
Reviewed-by: Philippe Ombredanne
Acked-By: Pierre-Louis Bossart
Reviewed
Add the SoundWire subsystem maintainer entry with details and
Sanyog and me as maintainers.
Signed-off-by: Sanyog Kale
Reviewed-by: Philippe Ombredanne
Acked-By: Pierre-Louis Bossart
Reviewed-by: Takashi Iwai
Signed-off-by: Vinod Koul
---
MAINTAINERS | 9 +
1 file changed, 9 insertio
Some Intel platforms have SoundWire Master, so add Intel SoundWire
Master driver which uses Cadence module. This patch adds probe and
initialization routines for Intel Master driver.
Signed-off-by: Hardik T Shah
Signed-off-by: Sanyog Kale
Reviewed-by: Philippe Ombredanne
Acked-By: Pierre-Louis
From: Sanyog Kale
SoundWire Slaves report status to bus. Add helpers to handle
the status changes.
Signed-off-by: Hardik T Shah
Signed-off-by: Sanyog Kale
Reviewed-by: Philippe Ombredanne
Acked-By: Pierre-Louis Bossart
Reviewed-by: Takashi Iwai
Signed-off-by: Vinod Koul
---
drivers/soundw
From: Sanyog Kale
Implement sdw_master_ops with support for xfer_msg, xfer_msg_defer
and reset_page_addr. Since Cadence module doesn't know the systems
it will be used, set the read_prop to the bus helper.
Signed-off-by: Hardik T Shah
Signed-off-by: Sanyog Kale
Reviewed-by: Philippe Ombredanne
Cadence IP implements SoundWire Master. Add base cadence library
initialization and interrupt handling
Signed-off-by: Hardik T Shah
Signed-off-by: Sanyog Kale
Reviewed-by: Philippe Ombredanne
Acked-By: Pierre-Louis Bossart
Reviewed-by: Takashi Iwai
Signed-off-by: Vinod Koul
---
drivers/soun
SoundWire bus supports read or write register(s) for SoundWire Slave
device. sdw_read() and sdw_write() APIs are provided for single
register read/write. sdw_nread() and sdw_nwrite() for operations on
contiguous registers.
Signed-off-by: Sanyog Kale
Reviewed-by: Philippe Ombredanne
Acked-By: Pie
From: Sanyog Kale
MIPI SoundWire spec defines standard SoundWire registers mandatory for
SoundWire Slave devices, so add them.
Signed-off-by: Sanyog Kale
Reviewed-by: Philippe Ombredanne
Acked-By: Pierre-Louis Bossart
Reviewed-by: Takashi Iwai
Signed-off-by: Vinod Koul
---
include/linux/so
From: Sanyog Kale
SoundWire is a new Linux bus which implements a new MIPI bus protocol
'SoundWire'. The summary of SoundWire bus and API is documented in the
'summary' file.
Signed-off-by: Sanyog Kale
Signed-off-by: Hardik T Shah
Reviewed-by: Philippe Ombredanne
Acked-By: Pierre-Louis Bossar
MIPI Discovery And Configuration (DisCo) Specification for SoundWire
specifies properties to be implemented for SoundWire Masters and
Slaves. The DisCo spec doesn't mandate these properties. However,
SDW bus cannot work without knowing these values.
The helper functions read the Master and Slave p
We are going to merge this series thru sound tree, need Mark's ack on
regmap patch or to take it thru regmap tree.
This patch series adds a new SoundWire subsystem which implements a
new MIPI bus protocol 'SoundWire'.
The SoundWire protocol is a robust, scalable, low complexity, low
power, low la
On Thu 30 Nov 08:46 PST 2017, Loic Pallardy wrote:
> Enable memory device creation for each memory region added
> by rproc_add_carveout function.
>
> Signed-off-by: Loic Pallardy
> ---
> drivers/remoteproc/st_remoteproc.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git
Hi
On 12/14/2017 12:57 PM, Jia He Wrote:
Hi Christoffer
I have tried your newer level-mapped-v7 branch, but bug is still there.
There is no special load in both host and guest. The guest (kernel
4.14) is often hanging when booting
the guest kernel log
[ OK ] Reached target Remote File Sys
On Thu 30 Nov 08:46 PST 2017, Loic Pallardy wrote:
> + /* By name */
> + mem = rproc_find_carveout_by_name(rproc, rsc->name);
> + if (mem) {
> + /*
> + * Update resource table with registered carevout information
> + */
> + rsc->len = me
On Thu, Dec 07, 2017 at 10:13:02AM -0800, Deepa Dinamani wrote:
> The series is aimed at making input events y2038 safe.
> It extends the lifetime of the realtime timestamps in the
> events to year 2106.
> The series is also a necessary update as glibc is set to provide
> 64 bit time_t support for
On Thu 30 Nov 08:46 PST 2017, Loic Pallardy wrote:
> This patch parse existing carveout list to find a memory area
> matching on "vdevbuffer" name.
> If found, memory device will be used as parent for vdev creation, else
> rproc platform device will be used as today.
>
> Signed-off-by: Loic Palla
It will be more helpful to add some tracepoints to track RTC actions when
debugging RTC driver. Below sample is that we set/read the RTC time, then
set 2 alarms, so we can see the trace logs:
set/read RTC time:
kworker/0:1-67 [000] 21.814245: rtc_set_time: UTC (1510301580) (0)
kworker/0:1-67 [000]
On 12/13/2017 06:52 PM, Jann Horn wrote:
> On Wed, Dec 13, 2017 at 10:31 AM, Michal Hocko wrote:
>> From: John Hubbard
>>
>> -- Expand the documentation to discuss the hazards in
>>enough detail to allow avoiding them.
>>
>> -- Mention the upcoming MAP_FIXED_SAFE flag.
>>
>> -
On 13-12-17, 10:44, Greg Kroah-Hartman wrote:
> And this feels really odd, does it really save any work for the
> individual "constraint" to check for this option? I'm all for helper
> functions, but this feels like more work than it's worth...
Ok, will move this code to individual platform drive
As you know, ocfs2 has support trim the underlying disk via
fstrim command. But there is a problem, ocfs2 is a shared disk
cluster file system, if the user configures a scheduled fstrim
job on each file system node, this will trigger multiple nodes
trim a shared disk simultaneously, it is very wast
Introduce a new dlm lock resource, which will be used to
communicate during fstrim a ocfs2 device from cluster nodes.
Signed-off-by: Gang He
---
fs/ocfs2/dlmglue.c | 86 +
fs/ocfs2/dlmglue.h | 29 +
fs/ocfs2/ocfs2.h
On Wed, Dec 13, 2017 at 04:06:11PM +, Mark Brown wrote:
> > On Mon, Dec 11, 2017 at 11:43:02PM +, srinivas.kandaga...@linaro.org
> > wrote:
>
> > Mark, can I get an Ack for this patch so I can take it through my tree
> > with the other patches in this series?
>
> I'm actually not seeing
Hi Ching,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on scsi/for-next]
[also build test WARNING on next-20171213]
[cannot apply to v4.15-rc3]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https
While testing on a large CPU system, detected the following RCU
stall many times over the span of the workload. This problem
is solved by adding a cond_resched() in the change_pte_range()
function.
[ 850.962530] INFO: rcu_sched detected stalls on CPUs/tasks:
[ 850.962584] 154-: (670 ticks t
On Wed, Dec 13, 2017 at 7:46 PM, Ingo Molnar wrote:
>
> * Byungchul Park wrote:
>
>> Lockdep works, based on the following:
>>
>>(1) Classifying locks properly
>>(2) Checking relationship between the classes
>>
>> If (1) is not good or (2) is not good, then we
>> might get false positives
Hi Christoffer
I have tried your newer level-mapped-v7 branch, but bug is still there.
There is no special load in both host and guest. The guest (kernel 4.14)
is often hanging when booting
the guest kernel log
[ OK ] Reached target Remote File Systems.
Starting File System Check on /dev/map
Hi Andrew,
On Wed, 13 Dec 2017 17:03:00 -0800 Andrew Morton
wrote:
>
> I'm probably sitting on an older version. I've dropped
>
> epoll: use the waitqueue lock to protect ep->wq
> sched/wait: assert the wait_queue_head lock is held in __wake_up_common
Dropped from linux-next as well.
--
Che
Linus Torvalds writes:
> On Wed, Dec 13, 2017 at 7:54 AM, Peter Zijlstra wrote:
>>
>> Which is why get_user_pages() _should_ enforce this.
>>
>> What use are protection keys if you can trivially circumvent them?
>
> No, we will *not* worry about protection keys in get_user_pages().
>
> They are
On 07-12-17, 14:19, Patrick Bellasi wrote:
> On 07-Dec 10:45, Viresh Kumar wrote:
> > On 30-11-17, 15:57, Patrick Bellasi wrote:
> > > Yes, that's a pretty trivial update with a confusing changelog.
> > >
> > > If we think it's worth to keep (and correct as well) I'll update the
> > > commit messa
Commit 8e55b6fd0660 ("staging: lustre: lnet: replace list_for_each
with list_for_each_entry") was intended to be an idempotent change,
but actually broke the behavior of ksocknal_add_peer() causing mounts to fail.
The fact that it caused an existing "route2 = NULL;" to become
redundant could have
+ Gautham,
@Gautham: Can you please help reviewing this one ?
On 13-12-17, 13:49, Abhishek Goel wrote:
> @@ -693,6 +746,8 @@ static int powernv_cpufreq_target_index(struct
> cpufreq_policy *policy,
> {
> struct powernv_smp_call_data freq_data;
> unsigned int cur_msec, gpstate_idx;
>
On Wed, Dec 13, 2017 at 03:47:03PM -0500, Steven Rostedt wrote:
> From: "Steven Rostedt (VMware)"
>
> The stack tracer records a stack dump whenever it sees a stack usage that is
> more than what it ever saw before. This can happen at any function that is
> being traced. If it happens when the CP
This patch enables a PiFi DAC+ V2.0, which is a PCM5122-based audio
output DAC add-on board for the Raspberry Pi B+ and later, connected
to the GPIO header of the Bananapi M3 via jumper cables. The power,
ground, and I2C pins are in the same position, but the I2S ones are
not.
The I2C controller u
The A83T has 3 I2C controllers under the standard bus. There is one
more in the R_ block section. The pin functions for the 3 controllers
are on PH 0~6. I2C2 can also be used on pins PE14 and PE15, but these
pins can also mux the CSI (camera sensor interface) controller's
embedded I2C controller. T
Hi everyone,
This is v2 of my A83T I2S and I2C support series.
Changes since v1:
- Dropped ASoC patch that was merged
- Added SoC-specific compatible strings for I2C controllers
- Added Maxime's Acked-by
This series adds support for I2S and I2C on the Allwinner A83T SoC.
The I2S controlle
The A83T has 3 I2S controllers. The first is multiplexed with the TDM
controller. The pins are generally connected to the codec side of the
AXP81x PMIC/codec/RTC chip. The second is free for other uses. The
third only supports output, and is connected internally to the HDMI
controller for HDMI audi
On Wed, Dec 13, 2017 at 7:29 PM, kernel test robot
wrote:
>
> FYI, we noticed the following commit (built with gcc-6):
>
> commit: b00b798255eb414246718eeec93d1ef10f894445 ("x86/fixmap: Add LDT
> entries to user-shared fixmap")
> https://git.kernel.org/cgit/linux/kernel/git/tip/tip.git WIP.x86/pt
From: Xiongwei Song
The function binder_alloc_new_buf_locked() is only used in this file, so
make it static. Also clean up sparse warning:
drivers/android/binder_alloc.c:330:23: warning: no previous prototype
for ‘binder_alloc_new_buf_locked’ [-Wmissing-prototypes]
In addition, the line of the
Sorry,
I think I know your meaning now.
Maybe we can unlock the spinlock before "schedule_timeout_interruptible"
and then lock again?
Like:
spin_unlock(...);
schedule_timeout_interruptible(1);
spin_lock(...);
Best wishes,
Jia-Ju Bai
On 2017/12/14 11:34, David Miller wrote:
Fro
On 12/13/2017 10:16 PM, Tetsuo Handa wrote:
Wei Wang wrote:
On 12/12/2017 09:20 PM, Tetsuo Handa wrote:
Wei Wang wrote:
+void xb_clear_bit_range(struct xb *xb, unsigned long start, unsigned long end)
+{
+ struct radix_tree_root *root = &xb->xbrt;
+ struct radix_tree_node *node;
+
On Thu, Dec 7, 2017 at 11:58 PM, Maxime Ripard
wrote:
> The A83T has a PWM that can be output from the SoC. Let's add a pinctrl
> group for it.
>
> Reviewed-by: Chen-Yu Tsai
> Signed-off-by: Maxime Ripard
Might as well just squash this with patch 11, and enforce it by default.
ChenYu
On Thu, Dec 7, 2017 at 11:58 PM, Maxime Ripard
wrote:
> The TCON supports the LVDS interface to output to a panel or a bridge.
> Let's add support for it.
>
> Signed-off-by: Maxime Ripard
> ---
> drivers/gpu/drm/sun4i/Makefile | 1 +-
> drivers/gpu/drm/sun4i/sun4i_lvds.c | 177
Hi,
On 12/14/2017 11:10 AM, Bob Liu wrote:
> On 2017/12/14 9:02, Lu Baolu wrote:
>> > From: Huang Ying
>> >
>> > Shared Virtual Memory (SVM) allows a kernel memory mapping to be
>> > shared between CPU and and a device which requested a supervisor
>> > PASID. Both devices and IOMMU units have TL
From: Jia-Ju Bai
Date: Thu, 14 Dec 2017 11:13:15 +0800
> Thanks for reply :)
> I think I should use "udelay(10/HZ)" instead, do you think it is
> right?
The delay is too long, please do not ignore that part of my critique
of your change.
You cannot delay so long under a lock, that's why the
1 - 100 of 1055 matches
Mail list logo
