On 16/11/2017 03:47, Viresh Kumar wrote:
> On 15-11-17, 19:17, Rafael J. Wysocki wrote:
>> However, I would like to see a clear declaration from whoever is
>> maintaining that code today that there is a plan in place to upstream
>> it and that this plan will actually be acted on. And, better yet,
On Fri, Nov 17, 2017 at 05:57:43AM +, Harninder Rai wrote:
> >
> > No, not at all, if you want a patch in a specific stable tree, just email
> > the git
> > commit id to sta...@vger.kernel.org and let me know what
> > tree(s) it should be applied to.
>
> You can drop this patch. Thanks Greg
On Fri, 17 Nov 2017 00:01:06 +0100,
Pierre-Louis Bossart wrote:
>
>
>
> On 11/16/2017 04:24 PM, Linus Torvalds wrote:
> > On Thu, Nov 16, 2017 at 2:16 PM, Pierre-Louis Bossart
> > wrote:
> >> Add 'default m' when sensible
> > No.
> >
> > This is not sensible, and is not at all what I suggested.
On Thu, Nov 16, 2017 at 08:46:01PM -0500, Pavel Tatashin wrote:
> There is no need to have ARCH_SUPPORTS_DEFERRED_STRUCT_PAGE_INIT,
> as all the page initialization code is in common code.
>
> Also, there is no need to depend on MEMORY_HOTPLUG, as initialization code
> does not really use hotplug
On Wed, Nov 15, 2017 at 02:10:36PM +, srinivas.kandaga...@linaro.org wrote:
> +void slim_msg_response(struct slim_controller *ctrl, u8 *reply, u8 tid, u8
> len)
> +{
> + struct slim_msg_txn *txn;
> + struct slim_val_inf *msg;
> + unsigned long flags;
> +
> + spin_lock_irqsave(
On 11/16/17, Jani Nikula wrote:
> On Wed, 15 Nov 2017, Tuncer Ayaz wrote:
> > I don't follow why you think it's a different platform and how I
> > might have "more" definitely shown v4.1 to be good, but I'll trust
> > your judgement as a drm dev and not argue :).
>
> You apparently have Sandy Bri
On Thursday, November 16, 2017 2:10:56 AM JST, Gustavo Padovan wrote:
From: Gustavo Padovan
If V4L2_BUF_FLAG_OUT_FENCE flag is present on the QBUF call we create
an out_fence and send its fd to userspace on the fence_fd field as a
return arg for the QBUF call.
The fence is signaled on buffer_d
On Thu, Nov 16, 2017 at 4:15 PM, Jonas Oberg wrote:
> Hi,
>
>> One other thing that occurred to me is that documentation files, too,
>> are copyrightable and should have license identifiers.
>
> Would it make sense to take an incremental approach to this? Get the
> source code and identifiers work
On Fri, Nov 17, 2017 at 07:18:45AM +, Liuwenliang (Abbott Liu) wrote:
> On 16/11/17 22:41 Marc Zyngier [mailto:marc.zyng...@arm.com] wrote:
> >No, it doesn't. It cannot work, because Cortex-A9 predates the invention
> >of the 64bit accessor. I suspect that you are testing stuff in QEMU,
> >whi
On 11/16/2017 11:18 AM, Michal Hocko wrote:
+ if (flags & MAP_FIXED_SAFE) {
+ struct vm_area_struct *vma = find_vma(mm, addr);
+
+ if (vma && vma->vm_start <= addr)
+ return -ENOMEM;
+ }
Could you pick a different error code which ca
On Friday, November 17, 2017 4:19:00 PM JST, Alexandre Courbot wrote:
On Thursday, November 16, 2017 2:10:55 AM JST, Gustavo Padovan wrote:
From: Gustavo Padovan
Add vb2_setup_out_fence() and the needed members to struct vb2_buffer.
v3:
- Do not hold yet another ref to the out_fence (
On 11/16/2017 03:46 PM, Masahiro Yamada wrote:
> Currently, KBUILD_MODNAME is defined only when $(modname) contains
> just one word. If an object is shared between multiple modules,
> undefined KBUILD_MODNAME causes a build error.
>
> A simple test case is as follows:
>
> obj-m += foo.o
>
On 16/11/17 22:41 Marc Zyngier [mailto:marc.zyng...@arm.com] wrote:
>No, it doesn't. It cannot work, because Cortex-A9 predates the invention
>of the 64bit accessor. I suspect that you are testing stuff in QEMU,
>which is giving you a SW model that always supports LPAE. I suggest you
>test this co
On Thursday, November 16, 2017 2:10:55 AM JST, Gustavo Padovan wrote:
From: Gustavo Padovan
Add vb2_setup_out_fence() and the needed members to struct vb2_buffer.
v3:
- Do not hold yet another ref to the out_fence (Brian Starkey)
v2: - change it to reflect fd_install at DQEVENT
> The middle of the merge window is the wrong time to send patches as
> maintaner attention is going to making certain the merge goes smoothly
> and nothing is missed.
Sorry Eric, please feel free to ignore the patch until you have time.
It is very difficult to figure out the correct time, since
kmemleak_scan will scan struct page for each node and it can be really
large and resulting in a soft lockup. We have seen a soft lockup when do
scan while compile kernel:
[ 220.561051] watchdog: BUG: soft lockup - CPU#53 stuck for 22s! [bash:10287]
[...]
[ 220.753837] Call Trace:
[ 220.7562
On Friday, November 17, 2017 4:02:56 PM JST, Alexandre Courbot wrote:
On Thursday, November 16, 2017 2:10:54 AM JST, Gustavo Padovan wrote:
From: Javier Martinez Canillas
Add a videobuf2-fence.h header file that contains different helpers
for DMA buffer sharing explicit fence support in videob
On Wed, Nov 15, 2017 at 02:10:35PM +, srinivas.kandaga...@linaro.org wrote:
> +
> + for_each_child_of_node(ctrl->dev->of_node, node) {
> + struct slim_device *sbdev;
> + struct slim_eaddr e_addr;
> + const char *compat = NULL;
> + int reg[2],
On 17/11/2017 00:35, Tony Krowiak wrote:
On 11/16/2017 03:25 PM, Pierre Morel wrote:
On 16/11/2017 18:03, Cornelia Huck wrote:
On Thu, 16 Nov 2017 17:06:58 +0100
Pierre Morel wrote:
On 16/11/2017 16:23, Tony Krowiak wrote:
On 11/14/2017 08:57 AM, Cornelia Huck wrote:
On Tue, 31 Oct 2017 15
On Thu 16 Nov 22:47 PST 2017, Jassi Brar wrote:
> On 16 Nov 2017 23:12, "Bjorn Andersson" wrote:
> On Thu 16 Nov 09:06 PST 2017, Jassi Brar wrote:
> > diff --git a/drivers/mailbox/mailbox.c b/drivers/mailbox/mailbox.c
> > index 674b35f..95e480e 100644
> > --- a/drivers/mailbox/mailbox.c
> > +++ b/
On Thursday, November 16, 2017 2:10:54 AM JST, Gustavo Padovan wrote:
From: Javier Martinez Canillas
Add a videobuf2-fence.h header file that contains different helpers
for DMA buffer sharing explicit fence support in videobuf2.
v2: - use fence context provided by the caller in vb2_fence_a
On Thu 16 Nov 22:36 PST 2017, kgu...@codeaurora.org wrote:
> On 2017-11-16 22:25, Bjorn Andersson wrote:
> > On Thu 16 Nov 04:18 PST 2017, Kiran Gunda wrote:
> >
> > > WLED driver provides the interface to the display driver to
> > > adjust the brightness of the display backlight.
> > >
> >
> >
On Thu, Nov 16, 2017 at 09:27:51PM +0800, Chris Chiu wrote:
> On Thu, Nov 16, 2017 at 8:44 PM, Mika Westerberg
> wrote:
> > On Wed, Nov 15, 2017 at 06:19:56PM +0800, Chris Chiu wrote:
> >> Hi Mika,
> >> I've confirmed with Asus and they said it's the latest BIOS for
> >> shipment and verified
On 16/11/17 21:50, Josh Poimboeuf wrote:
> On Wed, Oct 25, 2017 at 11:33:43AM +0200, Juergen Gross wrote:
>> On 04/10/17 17:58, Josh Poimboeuf wrote:
>>> Some of the paravirt '*_CLOBBERS' macros refer to output constraints
>>> instead of clobbers, which makes the code extra confusing. Rename the
>
This patch is to fix the 'dubious one-bit signed bitfield' error reported
by sparse, when using 'make C=2'.
Fixes: 799ba82de01e ("sched/deadline: Use C bitfields for the state flags")
Signed-off-by: Xin Long
---
include/linux/sched.h | 8
1 file changed, 4 insertions(+), 4 deletions(-)
Hi Gustavo,
I am coming a bit late in this series' review, so apologies if some of my
comments have already have been discussed in an earlier revision.
On Thursday, November 16, 2017 2:10:53 AM JST, Gustavo Padovan wrote:
From: Gustavo Padovan
Receive in-fence from userspace and add support f
2017-11-17 12:43 GMT+08:00 Shakeel Butt :
> On Thu, Nov 16, 2017 at 7:09 PM, Yafang Shao wrote:
>> Currently the default tmpfs size is totalram_pages / 2 if mount tmpfs
>> without "-o size=XXX".
>> When we mount tmpfs in a container(i.e. docker), it is also
>> totalram_pages / 2 regardless of the
hi,
On Thursday 16 November 2017 07:27 PM, Ian Abbott wrote:
On 16/11/17 04:32, Arvind Yadav wrote:
pnp_irq() and pnp_port_start() can fail here and we must check
its return value.
Signed-off-by: Arvind Yadav
---
drivers/staging/comedi/drivers/ni_atmio.c | 3 +++
1 file changed, 3 insertio
On 2017-11-16 22:25, Bjorn Andersson wrote:
On Thu 16 Nov 04:18 PST 2017, Kiran Gunda wrote:
WLED driver provides the interface to the display driver to
adjust the brightness of the display backlight.
Hi Kiran,
This driver has a lot in common with the already upstream
pm8941-wled.c,
becau
On Thu 16 Nov 04:11 PST 2017, Srinivas Kandagatla wrote:
> On 15/11/17 20:10, Bjorn Andersson wrote:
[..]
> > diff --git a/drivers/soc/qcom/Kconfig b/drivers/soc/qcom/Kconfig
> > index 91b70b170a82..9718f1c41e3d 100644
> > --- a/drivers/soc/qcom/Kconfig
> > +++ b/drivers/soc/qcom/Kconfig
> > @@ -37
Hi ,
I haven't heard from you for a long time. How are things with you?
Do you have new projects that need PCB?
I really hope that we can have chance to make boards for you and I am sure you
won't be disappointed.
You may have many suppliers but we are glad to send our quotation for your
referen
[...]
>> > +++ linux-pm/include/linux/pm.h
>> > @@ -559,6 +559,7 @@ struct pm_subsys_data {
>> > * NEVER_SKIP: Do not skip system suspend/resume callbacks for the device.
>> > * SMART_PREPARE: Check the return value of the driver's ->prepare
>> > callback.
>> > * SMART_SUSPEND: No need to r
On Thu 16 Nov 04:10 PST 2017, Srinivas Kandagatla wrote:
> On 15/11/17 20:10, Bjorn Andersson wrote:
[..]
> > diff --git a/drivers/soc/qcom/Kconfig b/drivers/soc/qcom/Kconfig
> > index b00bccddcd3b..91b70b170a82 100644
> > --- a/drivers/soc/qcom/Kconfig
> > +++ b/drivers/soc/qcom/Kconfig
> > @@ -35
Hi Lukas,
> John Stultz reports a boot time crash with the HiKey board (which uses
> hci_serdev) occurring in hci_uart_tx_wakeup(). That function is
> contained in hci_ldisc.c, but also called from the newer hci_serdev.c.
> It acquires the proto_lock in struct hci_uart and it turns out that we
>
On Thu 16 Nov 12:05 PST 2017, Chris Lew wrote:
> > + req.event = SSCTL_SSR_EVENT_BEFORE_SHUTDOWN;
>
> Are there plans to add the other SSR events to sysmon notifiers? I think the
> SSCTL service expects to receive events about remote procs starting as well.
>
We could easily add support here t
>
> No, not at all, if you want a patch in a specific stable tree, just email the
> git
> commit id to sta...@vger.kernel.org and let me know what
> tree(s) it should be applied to.
You can drop this patch. Thanks Greg
>
> thanks,
>
> greg k-h
On Thursday, November 16, 2017 2:10:49 AM JST, Gustavo Padovan wrote:
From: Gustavo Padovan
We use ordered_in_driver property to optimize for the case where
the driver can deliver the buffers in an ordered fashion. When it
is ordered we can use the same fence context for all fences, but
when it
On 2017/11/17 11:30, Yunlong Song wrote:
> How about add file_write_and_wait_range in __write_node_page as following:
> if (atomic && !test_opt(sbi, NOBARRIER)) {
> file_write_and_wait_range(file, 0, LLONG_MAX);
Nope, GCed encrypted data wouldn't be cached in inode page cache.
I don't think
On 16/11/17 22:19, Josh Poimboeuf wrote:
> On Wed, Oct 25, 2017 at 01:25:02PM +0200, Juergen Gross wrote:
>> On 04/10/17 17:58, Josh Poimboeuf wrote:
>>> Add alternative patching support for replacing an instruction with an
>>> indirect call. This will be needed for the paravirt alternatives.
>>>
The dt-bindings header was applied to the driver subsystem. I had to
wait for a merge window to use it from DT.
Signed-off-by: Masahiro Yamada
---
arch/arm/boot/dts/uniphier-ld4-ref.dts | 2 +-
arch/arm/boot/dts/uniphier-ld4.dtsi | 2 ++
arch/arm/boot/dts/uniphier-ld6b-ref.dts | 2 +-
arc
gmail for some reason ate my email formatting, apparantly preediting
in gedit, then pasting in here doesn't work so well.
Dave.
On 17 November 2017 at 14:05, Dave Airlie wrote:
> Hi Linus,
>
> This is the pull request for the AMD DC (display code) layer which is
> a requirement
> to program the
On 2017/11/17 10:13, Tan Xiaojun wrote:
> On 2017/11/16 23:23, Sudeep Holla wrote:
>>
>>
>> On 16/11/17 12:58, Tan Xiaojun wrote:
>>> Since commit dfea747d2aba ("drivers: base: cacheinfo: support DT
>>> overrides for cache properties"), we can set the correct cacheinfo
>>> via DT. But the cache typ
These were added to make the ARM64 branch self-contained because
updates for ARM and ARM64 are supposed to be sent as separate
pull requests.
Now, they were merged together in Linus' tree and interrupt-parent
from the arch/arm/boot/dts/uniphier-support-card.dtsi is visible from
ARM64 DT files by t
The dt-bindings header was applied to the driver subsystem. I had to
wait for a merge window to use it from DT.
Signed-off-by: Masahiro Yamada
---
arch/arm64/boot/dts/socionext/uniphier-ld11-ref.dts | 2 +-
arch/arm64/boot/dts/socionext/uniphier-ld11.dtsi| 3 ++-
arch/arm64/boot/dts/socion
Commit 15e85695e500 ("arm64: dts: uniphier: add GPIO hog definition")
missed to update the PXs3 DTS for some reason. Do it now.
Signed-off-by: Masahiro Yamada
---
arch/arm64/boot/dts/socionext/uniphier-pxs3-ref.dts | 8
1 file changed, 8 insertions(+)
diff --git a/arch/arm64/boot/dts
From: Jason Wang
Date: Fri, 17 Nov 2017 10:55:44 +0800
>
>
> On 2017年11月17日 10:46, Joel Stanley wrote:
>> Looks like this was mistakenly added to the tree as part of
>> commit 186b3c998c50 ("virtio-net: support XDP_REDIRECT").
>>
>> Signed-off-by: Joel Stanley
>> ---
>> drivers/net/virtio_ne
On 11/16, Michael S. Tsirkin wrote:
>On Thu, Nov 16, 2017 at 08:58:13AM +0800, kernel test robot wrote:
>>
>> FYI, we noticed the following commit (built with gcc-6):
>>
>> commit: 05b5d5161b9e6c72e1d06f36614edbdbfe192cc7 ("fw_cfg: do DMA read
>> operation")
>> https://git.kernel.org/cgit/linux/
On Thu, Nov 16, 2017 at 01:44:00PM -0700, Jason Gunthorpe wrote:
> As was discussed in September and October, add Jason along with
> Doug to have a team maintainership model for the RDMA subystem.
>
> Mellanox Technologies will be funding Jason's independent work on
> the maintainership.
>
> Signed
Hey Folks,
So, for awhile recently, I've noticed my HiKey board (which uses the
TI WL1835MOD chip for wifi) has had trouble when it tries to suspend.
Basically it keeps on waking up while suspending, and then
re-suspending over and over until it lucks out in whatever race is
going on and manages
At Linaro we’ve been putting effort into regularly running kernel tests over
arm, arm64 and x86_64 targets. On those targets we’re running mainline, -next,
4.4, and 4.9 kernels and yes we are adding to this list as the hardware
capacity grows.
For test buckets we’re using just LTP, kselftest an
On Thu, 2017-11-16 at 14:57 -0800, Kees Cook wrote:
> On Thu, Nov 16, 2017 at 9:01 AM, Knut Omang wrote:
> > The most important checkpatch feature added is the --ignore-cfg feature,
> > which
> > takes a file argument and parses that file according to this minimal
> > language:
> >
> >#
On Thu, Nov 16, 2017 at 7:09 PM, Yafang Shao wrote:
> Currently the default tmpfs size is totalram_pages / 2 if mount tmpfs
> without "-o size=XXX".
> When we mount tmpfs in a container(i.e. docker), it is also
> totalram_pages / 2 regardless of the memory limit on this container.
> That may easil
On Thu, Nov 16, 2017 at 05:29:35PM +, Srinivas Kandagatla wrote:
> thanks for the comments.
>
>
> On 16/11/17 16:42, Vinod Koul wrote:
> >On Wed, Nov 15, 2017 at 02:10:34PM +, srinivas.kandaga...@linaro.org
> >wrote:
> >
> >>+static void slim_dev_release(struct device *dev)
> >>+{
> >>+
On Thu, Nov 16, 2017 at 08:15:15PM -0800, John Stultz wrote:
> On Thu, Nov 16, 2017 at 6:06 PM, Leo Yan wrote:
> > Hi John,
> >
> > On Thu, Nov 16, 2017 at 05:58:54PM -0800, John Stultz wrote:
> >> On Thu, Nov 16, 2017 at 5:54 PM, John Stultz
> >> wrote:
> >> > Testing with Linus' HEAD today on
The rps_resp buffer in ata_device is a DMA target, but it isn't
explicitly cacheline aligned. Due to this, adjacent fields can be
overwritten with stale data from memory on non-coherent architectures.
As a result, the kernel is sometimes unable to communicate with an
SATA device behind a SAS expand
Hi all,
Please do not add any v4.16 material to your linux-next included trees
until v4.15-rc1 has been released.
Changes since 20171116:
The vfs tree gained a conflict against Linus' tree.
Non-merge commits (relative to Linus' tree): 3321
2505 files changed, 198683 insertions
Currently, MIPS is an architecture which support coherent & noncoherent
devices co-exist. So implement get_cache_alignment() function pointer
in 'struct dma_map_ops' to return different dma alignments.
Signed-off-by: Huacai Chen
---
arch/mips/cavium-octeon/dma-octeon.c| 3 ++-
arch/m
In non-coherent DMA mode, kernel uses cache flushing operations to
maintain I/O coherency, so scsi's block queue should be aligned to
ARCH_DMA_MINALIGN. Otherwise, If a DMA buffer and a kernel structure
share a same cache line, and if the kernel structure has dirty data,
cache_invalidate (no writeb
On 11/16/17 at 02:54P, Rafael J. Wysocki wrote:
> On Thursday, November 16, 2017 10:50:36 AM CET WANG Chao wrote:
> > On 11/16/17 at 01:24P, Rafael J. Wysocki wrote:
> > > On Wednesday, November 15, 2017 10:33:47 AM CET WANG Chao wrote:
> > > > On 11/15/17 at 02:13P, Rafael J. Wysocki wrote:
> > >
Make dma_get_cache_alignment() to accept a 'dev' argument. As a result,
it can return different alignments due to different devices' I/O cache
coherency.
Currently, ARM/ARM64 and MIPS support coherent & noncoherent devices
co-exist. This may be extended in the future, so add a new function
pointer
On Thu, Nov 16, 2017 at 8:50 AM, Shaohua Li wrote:
> On Tue, Nov 14, 2017 at 03:10:22PM -0800, Khazhismel Kumykov wrote:
>> Allows configuration additional bytes or ios before a throttle is
>> triggered.
>>
>> This allows implementation of a bucket style rate-limit/throttle on a
>> block device. P
On Thu, Nov 16, 2017 at 6:06 PM, Leo Yan wrote:
> Hi John,
>
> On Thu, Nov 16, 2017 at 05:58:54PM -0800, John Stultz wrote:
>> On Thu, Nov 16, 2017 at 5:54 PM, John Stultz wrote:
>> > Testing with Linus' HEAD today on the HiKey board, I started seeing boot
>> > hangs:
>> > ...
>> >
>> > [0.6
On Fri, Nov 17, 2017 at 01:16:36PM +1030, Joel Stanley wrote:
> Looks like this was mistakenly added to the tree as part of
> commit 186b3c998c50 ("virtio-net: support XDP_REDIRECT").
>
> Signed-off-by: Joel Stanley
Acked-by: Michael S. Tsirkin
> ---
> drivers/net/virtio_net. | 0
> 1 file ch
The Dell SMBIOS WMI interface will fail for some more complex calls unless
a WMI hotfix has been included. Most platforms have this fix available in
a maintenance BIOS release. In the case the driver is loaded on a
platform without this fix, disable the userspace interface.
A hotfix indicator is
On Fri, 2017-11-17 at 11:58 +0800, Axel Lin wrote:
> 2017-11-16 19:23 GMT+08:00 Keerthy :
> >
> >
> > On Monday 13 November 2017 06:22 PM, Axel Lin wrote:
> > > Signed-off-by: Axel Lin
> >
> > One line commit message would be better than blank commit message.
>
> It's just too trivial and chec
>Is this "hotfix" the same thing as "having the latest firmware
>installed" ?
>If so, making that clear in the dev_warn messages would be more useful
>to the person reading the log.
Yes, I'll modify and re-send.
On Thu, Nov 16, 2017 at 08:25:47AM -0800, Joe Perches wrote:
> Using const reduces data.
>
> $ size sound/soc/fsl/fsl_asrc.o*
>text data bss dec hex filename
> 21691 5872 192 277556c6b sound/soc/fsl/fsl_asrc.o.new
> 21435 6128 192 2775
Hi Linus,
This is the pull request for the AMD DC (display code) layer which is
a requirement
to program the display engines on the new Vega and Raven based GPUs.
It also contains
support for all amdgpu supported GPUs (CIK, VI, Polaris), which you
have to enable.
It is also a kms atomic modesettin
2017-11-16 19:23 GMT+08:00 Keerthy :
>
>
> On Monday 13 November 2017 06:22 PM, Axel Lin wrote:
>> Signed-off-by: Axel Lin
>
> One line commit message would be better than blank commit message.
It's just too trivial and checkpatch does not complain.
On Thu, Nov 16, 2017 at 01:40:13PM +, Srinivas Kandagatla wrote:
> Thanks for the review comments.
>
> On 16/11/17 13:09, Vinod Koul wrote:
> >On Wed, Nov 15, 2017 at 02:10:32PM +, srinivas.kandaga...@linaro.org
> >wrote:
> >>From: Sagar Dharia
> >
> >>+
> >>+Child nodes:
> >>+Every SLIM
Hi all,
On Fri, 17 Nov 2017 09:44:39 +1100 Stephen Rothwell
wrote:
>
> On Mon, 13 Nov 2017 12:43:08 +0100 Arnd Bergmann wrote:
> >
> > On Mon, Nov 13, 2017 at 9:09 AM, Michal Hocko wrote:
> > > On Mon 13-11-17 16:42:06, Stephen Rothwell wrote:
> > >>
> > >> After merging the akpm-current
On Thu, Nov 16, 2017 at 05:24:37PM +, Mark Brown wrote:
> On Thu, Nov 16, 2017 at 10:32:21PM +0530, Vinod Koul wrote:
> > On Thu, Nov 16, 2017 at 04:05:17PM +, Srinivas Kandagatla wrote:
>
> > > >+static const struct sdw_device_id *
> > > >+sdw_get_device_id(struct sdw_slave *slave, struct
On Fri, Sep 8, 2017 at 1:43 PM, Dan Williams wrote:
> On Thu, Sep 7, 2017 at 6:59 PM, Bob Liu wrote:
>> On 2017/9/8 1:27, Jerome Glisse wrote:
> [..]
>>> No this are 2 orthogonal thing, they do not conflict with each others quite
>>> the contrary. HMM (the CDM part is no different) is a set of he
How about add file_write_and_wait_range in __write_node_page as following:
if (atomic && !test_opt(sbi, NOBARRIER)) {
file_write_and_wait_range(file, 0, LLONG_MAX);
fio.op_flags |= REQ_PREFLUSH | REQ_FUA;
}
The all the GCed data will be flushed to non-volatile before last node
write with
On 2017/11/17 11:04, Yunlong Song wrote:
> The atomic commit will trigger:
> -f2fs_do_sync_file(filp, 0, LLONG_MAX, 0, true)
> -file_write_and_wait_range(file, 0, LLONG_MAX)
> -fsync_node_pages
> -__write_node_page
> -REQ_PREFLUSH | REQ_FUA
>
>
Currently the default tmpfs size is totalram_pages / 2 if mount tmpfs
without "-o size=XXX".
When we mount tmpfs in a container(i.e. docker), it is also
totalram_pages / 2 regardless of the memory limit on this container.
That may easily cause OOM if tmpfs occupied too much memory when swap is
off.
Nicolas Pitre cramfs work.
The following changes since commit 8a5776a5f49812d29fe4b2d0a2d71675c3facf3f:
Linux 4.14-rc4 (2017-10-08 20:53:29 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git work.cramfs
for you to fetch changes
The atomic commit will trigger:
-f2fs_do_sync_file(filp, 0, LLONG_MAX, 0, true)
-file_write_and_wait_range(file, 0, LLONG_MAX)
-fsync_node_pages
-__write_node_page
-REQ_PREFLUSH | REQ_FUA
So data is flushed to non-volatile before last node write wi
Assorted stuff, really no common topic here.
The following changes since commit 2bd6bf03f4c1c59381d62c61d03f6cc3fe71f66e:
Linux 4.14-rc1 (2017-09-16 15:47:51 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git work.misc
for you
A bunch of places switched to get_user_pages_fast().
The following changes since commit 2bd6bf03f4c1c59381d62c61d03f6cc3fe71f66e:
Linux 4.14-rc1 (2017-09-16 15:47:51 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git
work.get_u
On 2017年11月17日 10:46, Joel Stanley wrote:
Looks like this was mistakenly added to the tree as part of
commit 186b3c998c50 ("virtio-net: support XDP_REDIRECT").
Signed-off-by: Joel Stanley
---
drivers/net/virtio_net. | 0
1 file changed, 0 insertions(+), 0 deletions(-)
delete mode 100644
On 2017-11-17 01:50, Paolo Bonzini wrote:
On 16/11/2017 15:28, Quan Xu wrote:
vcpu->srcu_idx = srcu_read_lock(&kvm->srcu);
+ kvm_load_guest_fpu(vcpu);
+
for (;;) {
if (kvm_vcpu_running(vcpu)) {
r = vcpu_enter_guest(vcpu);
<<
as
Sorry for the delay. I thought all of the comments were straightforward, but
there are a couple which need some further discussion.
On Fri, Oct 20, 2017 at 12:45 PM, Rob Herring wrote:
> On Thu, Oct 19, 2017 at 5:50 PM, Brendan Higgins
> wrote:
>> Add a common device tree for all Nuvoton NPCM750
* bio_{map,copy}_user_iov() series; those are cleanups - fixes from
the same pile went into mainline (and stable) in late September.
* fs/iomap.c iov_iter-related fixes
* new primitive - iov_iter_for_each_range(); apply a function to
kernel-mapped segments of an iov_iter. U
On 2017/11/17 8:58, Yunlong Song wrote:
> Is there any problem if just deleting the judgement condition in this patch?
IIRC, dirty node comes from data segment GC can be writebacked & flushed during
atomic commit, but related data will still be in inner bio cache, after later
SPOR, data would be i
Looks like this was mistakenly added to the tree as part of
commit 186b3c998c50 ("virtio-net: support XDP_REDIRECT").
Signed-off-by: Joel Stanley
---
drivers/net/virtio_net. | 0
1 file changed, 0 insertions(+), 0 deletions(-)
delete mode 100644 drivers/net/virtio_net.
diff --git a/drivers/net
On Fri, 17 Nov 2017 09:23:18 +0800 Miles Chen wrote:
> On Thu, 2017-11-16 at 16:13 -0800, Andrew Morton wrote:
> > On Fri, 17 Nov 2017 06:56:12 +0800 wrote:
> >
> > > From: Miles Chen
> > >
> > > dma-debug reports the following warning:
> > >
> > > [name:panic&]WARNING: CPU: 3 PID: 298 at ke
On 11/10, Randy Dunlap wrote:
> On 11/10/2017 05:45 PM, Stephen Boyd wrote:
> > It isn't clear if this function of_node_put()s the 'from'
> > argument, or the node it finds in the search. Clearly indicate
> > which variable is touched.
> >
> > Signed-off-by: Stephen Boyd
> > ---
> > drivers/of/b
On 11/14, Stephen Boyd wrote:
> On 11/10, Catalin Marinas wrote:
> > On Wed, Nov 08, 2017 at 11:00:29AM -0800, Stephen Boyd wrote:
> > > The Kryo CPUs are also affected by the Falkor 1003 errata, so
> > > we need to do the same workaround on Kryo CPUs. The MIDR is
> > > slightly more complicated he
{get,put}_compat_sigset() series + assorted compat ioctl stuff +
more set_fs() elimination + a few more timespec64 conversions + several
removals of pointless access_ok() in places where it was followed only by
non-__ variants of primitives.
One conflict (in drivers/staging/pi433);
On Tue, Sep 26, 2017 at 03:54:51PM +0900, Byungchul Park wrote:
> It would be somewhat safer to put parentheses around parameters of
> a macro with parameters. Put it.
Hello Ingo and Peter,
Even though Huang said this change is unnecessary, I'm curious about
what you think about this fix.
As Hua
FYI, we noticed the following commit (built with gcc-6):
commit: c21f87074dc24c9e5a13dc63918b2d30891d190f ("lib/rbtree-test: lower
default params")
https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git master
in testcase: boot
on test machine: qemu-system-x86_64 -enable-kvm -smp 2 -
On Thursday, November 16, 2017 4:42 PM, Dan Murphy wrote:
>
> Jacek
>
> On 11/16/2017 02:14 PM, Jacek Anaszewski wrote:
> > Hi Dan and Pavel,
> >
> > On 11/15/2017 11:23 PM, Pavel Machek wrote:
> >> Hi!
> >>
> Shouldn't the driver be targeted for backlight subsystem then?
>
> Addin
Hi Thomas,
Any comments for this patch series?
Thanks,
Kan
>
> From: Kan Liang
>
> There are two free running counters for client IMC uncore. The custom
> event_init() function hardcode their index to 'UNCORE_PMC_IDX_FIXED' and
> 'UNCORE_PMC_IDX_FIXED + 1'. To support the 'UNCORE_PMC_IDX_FIXE
> On Nov 16, 2017, at 6:38 AM, Khalid Aziz wrote:
>
> Changelog v10:
>
> - Patch 1/10: Updated si_codes definitions for SEGV to match 4.14
> - Patch 2/10: No changes
> - Patch 3/10: Updated copyright
> - Patch 4/10: No changes
> - Patch 5/10: No changes
> - P
On 2017/11/16 23:23, Sudeep Holla wrote:
>
>
> On 16/11/17 12:58, Tan Xiaojun wrote:
>> Since commit dfea747d2aba ("drivers: base: cacheinfo: support DT
>> overrides for cache properties"), we can set the correct cacheinfo
>> via DT. But the cache type can't be set in the same way.
>>
>> I found
On 2017/11/14 17:24, Jan Kara wrote:
> On Tue 14-11-17 11:43:49, Chao Yu wrote:
>> On 2017/11/13 17:18, Jan Kara wrote:
>>> On Mon 13-11-17 11:31:48, Chao Yu wrote:
Commit 6184fc0b8dd7 ("quota: Propagate error from ->acquire_dquot()")
missed to handle error from dquot_initialize in dquot_
From: Kuninori Morimoto
SYS/RT/Audio DMAC includes independent data buffers for reading
and writing. Therefore, the read transfer counter and write transfer
counter have different values.
TCR indicates read counter, and TCRB indicates write counter.
The relationship is like below.
From: Kuninori Morimoto
DMAC reads data from source device, and buffered it until transferable
size for sink device. Because of this behavior, DMAC is including
buffered data .
Now, CHCR DE bit is controlling DMA transfer enable/disable.
If DE bit was cleared during data transferring, or during
Hi Vinod
Cc Geert, Laurent
These are v3 of dmaengine fixup for Renesas SoC.
Main diffs are fixup typo
Kuninori Morimoto (2):
dmaengine: rcar-dmac: ensure CHCR DE bit is actually 0 after clearing
dmaengine: rcar-dmac: use TCRB instead of TCR for residue
drivers/dma/sh/rcar-dmac.c | 44 +
1 - 100 of 906 matches
Mail list logo
