25Mhz MCLK which was earlier used was of spread type.
Thus, we were not getting accurate rate. The 48Mhz system
clk is of non-spread type and we are changing to it to get
accurate rate.
Signed-off-by: Akshu Agrawal
---
sound/soc/amd/acp-da7219-max98357a.c | 2 +-
1 file changed, 1 insertion(+),
Zong Li 於 2018年8月20日 週一 上午10:15寫道：
>
> This patches remove the implementation of NDS32_ABI_2 and
> replace the magic number of offset of lp on stack.
>
> In stacktrace.c, we dump the stack without considering the old
> ABI, it should be consistent in traps.c.
>
> Zong Li (2):
> nds32: Remove the
Zong Li 於 2018年8月15日 週三 下午5:35寫道：
>
> This patch set implements the ftrace function and function graph tracer
> on NDS32 architecture. We try to use C code to do everything, so we don't
> need to separate the implementation to assembly code and C code, we just
> need one ftrace.c file.
>
> In mcou
Zong Li 於 2018年8月13日 週一 下午5:27寫道：
>
> These patches fix the issue of expand macro with pointer argument,
> clean up the coding style and refactor the macro by extracting the
> checking and getting pointer to another macro definition.
>
>
> Zong Li (3):
> nds32: Fix get_user/put_user macro expand
On Mon, 20 Aug 2018 09:49:59 -0600
Lina Iyer wrote:
> On Mon, Aug 20 2018 at 09:34 -0600, Marc Zyngier wrote:
> >On 20/08/18 16:26, Lina Iyer wrote:
> >> On Sat, Aug 18 2018 at 07:13 -0600, Marc Zyngier wrote:
> >>> Hi Lina,
> >>>
> >>> On Fri, 17 Aug 2018 20:10:23 +0100,
> >>> Lina Iyer wro
We need that to adjust the len of the 2nd transfer (called data in spi-mem)
if it's too long to fit in a SPI message or SPI transfer.
Fixes: c36ff266dc82 ("spi: Extend the core to ease integration of SPI memory
controllers")
Cc:
Signed-off-by: Boris Brezillon
Signed-off-by: Chuanhua Han
-
Hi Frank,
2018-08-21 14:37 GMT+09:00 Frank Rowand :
> On 08/20/18 19:08, Masahiro Yamada wrote:
>> Hi Frank,
>>
>> 2018-08-21 10:31 GMT+09:00 Frank Rowand :
>>> On 08/20/18 14:32, Rob Herring wrote:
On Mon, Aug 20, 2018 at 1:55 PM Frank Rowand
wrote:
>
> On 07/03/18 18:59, Mas
On Tue, Aug 21, 2018 at 08:21:14AM +0200, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 4.9.123 release.
> There are 25 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know
On Tue, Aug 21, 2018 at 07:47:04AM +0200, Lukas Wunner wrote:
> On Mon, Aug 20, 2018 at 06:06:24PM -0500, Bjorn Helgaas wrote:
> > mmyan...@gmail.com reported a problem [1]: on v4.17, a QCA9005 AR9462
> > wifi device was present at boot, but disappeared after suspend/resume.
> >
> > He also tested
Hi Ravi,
On 2018-08-20 17:34, RaviChandra Sadineni wrote:
> Currently on every resume we check for mkbp events and notify the
> clients. This helps in identifying the wakeup sources. But on devices
> that do not support mkbp protocol, we might end up querying key state of
> the keyboard in a loop
Add GCOV_PROFILE_FTRACE to allow gcov profiling
on only files in ftrace subsystem. This config
option will be used for checking kselftest/ftrace
coverage.
Signed-off-by: Masami Hiramatsu
---
Changes in v2.1:
- Fix description according to Steve's comment.
---
kernel/trace/Kconfig | 12
Hi,
Thanks for the patch...
>
> In axidma alloc_chan_resources merge BD and cyclic BD allocation.
>
> Signed-off-by: Radhey Shyam Pandey
> Signed-off-by: Michal Simek
Acked-for-series: Appana Durga Kedareswara rao
Regards,
Kedar.
> ---
> drivers/dma/xilinx/xilinx_dma.c | 36 +++
Hi Naga,
> > And why is it an s32 and not a u32?
> To monitor NAND_CMD_STATUS.
> Sometimes core will just send status command without reading back the status
> data and later
> It will try to read one byte using ->exec_op().
> So Arasan has FLASH_STS register and whenever we initiate a status c
Song Liu wrote:
I am testing the patch set with the following code:
#include
#include
volatile short semaphore = 0;
int for_uprobe(int c)
{
printf("%d\n", c + 10);
return c + 1;
}
int main(int argc, char *argv[])
{
for_uprobe(argc);
while (1) {
Am Dienstag, 21. August 2018, 08:57:44 CEST schrieb liu.son...@zte.com.cn:
> Hi Richard,
>
> In ubifs_log_start_commit, the value of c->lhead_offs is zero or set to zero
> by code bellow
> 409 /* Switch to the next log LEB */
> 410 if (c->lhead_offs) {
> 411 c->lhe
On Thu, Aug 16, 2018 at 11:51:03AM +0530, Anup Patel wrote:
> Having thought about this more, I think cpu_ops should be an pointer array
> of NR_CPUS size. This means its not necessary to have have same ops for
> all CPUs. The ARM64 implementation of CPU operations also allows separate
> CPU operat
On Wed, Aug 15, 2018 at 04:56:16PM -0700, Atish Patra wrote:
> CPU hotplug code in smpboot requires interrupt cause
> to identify the cause of cpu wakeup.
>
> Move the IRQ cause declarations to appropriate header
> file.
asm/irq.h is a header indirectly included by just about every
driver. This
> if (!err) {
> +
> +#ifdef CONFIG_HOTPLUG_CPU
> + arch_send_call_function_single_ipi(cpu);
> +#endif
Please just provide a stub version of arch_send_call_function_single_ipi
for the !CONFIG_HOTPLUG_CPU case instead of the ifdef here.
> +#ifdef CONFIG_HOTPLUG_CPU
> +int can_hotp
On 2018-08-21 08:24, Sergey Senozhatsky wrote:
> +/**
> + * sysfs_strncpy - Trim a length-limited C-string (wgutesoaces and a trailing
> + * newline symbol) and copy into a buffer
> + * @dest: Where to copy the string to
> + * @src: Where to copy the string from
> + * @count: The ma
Below is the list of build error/warning regressions/improvements in
v4.18[1] compared to v4.17[2].
Summarized:
- build errors: +3/-1
- build warnings: +258/-46409
JFYI, when comparing v4.18[1] to v4.18-rc8[3], the summaries are:
- build errors: +2/-0
- build warnings: +105/-71
Note that
On 13.08.2018 23:48, Tony Krowiak wrote:
> From: Tony Krowiak
>
> Introduces a new CPU model feature and two CPU model
> facilities to support AP virtualization for KVM guests.
>
> CPU model feature:
>
> The KVM_S390_VM_CPU_FEAT_AP feature indicates that
> AP instructions are available on the g
On Tue, Aug 21, 2018 at 10:02 AM Geert Uytterhoeven
wrote:
> JFYI, when comparing v4.18[1] to v4.18-rc8[3], the summaries are:
> - build errors: +2/-0
Holiday season?
+ error: "__sanitizer_cov_trace_cmpd"
[drivers/gpu/drm/amd/amdgpu/amdgpu.ko] undefined!: => N/A
+ error: "__sanitizer_cov_
On Fri, Aug 17, 2018 at 2:40 AM Stephen Rothwell wrote:
> Today's linux-next merge of the mfd tree got a conflict in:
>
> MAINTAINERS
>
> between commit:
>
> 16b7db4c8150 ("MAINTAINERS: Add .clang-format entry")
>
> from Linus' tree and commit:
>
> 97c2b5cba204 ("mfd: madera: Add register de
Thanks for noticing, and sending this patch. I'm happy to see others
testing with Clang. I noticed this too near the end of the day
https://github.com/ClangBuiltLinux/linux/issues/27.
On Mon, Aug 20, 2018 at 11:48 PM Masahiro Yamada
wrote:
>
> Commit cafa0010cd51 ("Raise the minimum required gc
On Fri, Jul 20, 2018 at 5:42 AM Stephen Rothwell wrote:
> Today's linux-next merge of the mfd tree got a conflict in:
>
> drivers/gpu/drm/i915/Kconfig
>
> between commit:
>
> a57942bfdd61 ("ALSA: hda: Make audio component support more generic")
>
> from the sound tree and commit:
>
> 9c22912
On 08/19/2018 03:25 PM, Nick Desaulniers wrote:
> + gbiv who wrote this cool paste (showing alternatives to
> _Static_assert, which is supported by both compilers in -std=gnu89,
> but not until gcc 4.6): https://godbolt.org/g/DuLsxu
>
> I can't help but think that BUILD_BUG_ON_MSG should use
> _Sta
On Mon, Aug 20, 2018 at 12:14:58AM +0800, Pu Wen wrote:
> To make AMD64 EDAC and MCE drivers working on Hygon platforms, add
> vendor checking for Hygon by using the code path of AMD 0x17. Add a
> vendor field to struct amd64_pvt and initialize it in per_family_init
> for vendor checking.
>
> Also
Currently in record mode the tool implements trace writing serially.
The algorithm loops over mapped per-cpu data buffers and stores ready
data chunks into a trace file using write() system call.
At some circumstances the kernel may lack free space in a buffer
because the other buffer's half is
Commit 49aa76b16676 ("mtd: rawnand: do not execute nand_scan_ident()
if maxchips is zero") gave a new meaning for calling nand_scan_ident()
with maxchips=0.
It is a special usage for some drivers such as docg4, but in fact
the Denali driver may pass maxchips=0 to nand_scan() when the driver
is ena
The data buffer and accompanying AIO control block are allocated at
perf_mmap object and the mapped data buffer size is equal to
the kernel one.
The buffer is then used to preserve profiling data ready for dumping
and queue it for asynchronous writing into perf trace thru implemented
record__a
Trace file offsets are different for every enqueued write operation
and calculated dynamically in trace streaming loop and don't overlap
so write requests can be written in parallel.
record__mmap_read_sync implements sort of a barrier between spilling
ready profiling data to disk.
Signed-off
On Thu, Aug 16, 2018 at 8:05 PM Stephen Rothwell wrote:
> On Thu, 26 Jul 2018 15:10:06 +1000 Stephen Rothwell
> wrote:
> > Today's linux-next merge of the mfd tree got a conflict in:
> >
> > drivers/gpu/drm/i915/intel_display.h
> >
> > between commit:
> >
> > 6075546f57f8 ("drm/i915/icl: sto
On 13.08.2018 23:48, Tony Krowiak wrote:
> From: Pierre Morel
>
> Shadowing the crypto control block now supports APCB shadowing.
>
> AP instruction interpretation for guest 3 through ECA.28 is shadowed when
> guest 2 ECA.28 is set.
>
> CRYCB is shadowed for APCB and wrapping keys.
>
> CRYCB f
Hi Geert,
On Tue, 21 Aug 2018 10:08:54 +0200 Geert Uytterhoeven
wrote:
>
> To obey sorting rules, the CIRRUS LOGIC entry should be before the CLANG
> entry.
> Upon closer look, it should be inserted before the CISCO entries, too (in
> the mfd tree).
Thanks for noticing. Unfortunately it is bad
On Fri, Jul 20, 2018 at 06:06:57PM +0800, Anson Huang wrote:
> Add "gpio-ranges" property to establish connections between GPIOs
> and PINs on i.MX6SLL pinctrl driver, for details, please refer to
> Documentation/devicetree/bindings/gpio/gpio.txt of "gpio-ranges"
> property.
>
> Signed-off-by: Ans
On Sunday, August 12, 2018 6:09:27 PM CEST Leo Yan wrote:
> The usage for two variables 'data->predicted_us' and 'expected_interval'
> in menu_select() are confused, especially these two variables are
> assigned with each other: firstly 'data->predicted_us' is assigned to
> the minimum value betwee
On Sunday, August 12, 2018 6:09:28 PM CEST Leo Yan wrote:
> Since the tick delta is used in multiple places in menu_select(), it's
> better to use single one variable to record this value; furthermore, for
> more readable we can refactor the code to split a separate function to
> making decision fo
On 21/08/18 00:19, Bjorn Andersson wrote:
> On Fri 17 Aug 12:10 PDT 2018, Lina Iyer wrote:
>> diff --git
>> a/Documentation/devicetree/bindings/pinctrl/qcom,sdm845-pinctrl.txt
>> b/Documentation/devicetree/bindings/pinctrl/qcom,sdm845-pinctrl.txt
> [..]
>> @@ -155,11 +166,52 @@ Example:
>> t
2018-08-17 20:44 GMT+03:00 Matwey V. Kornilov :
> пт, 10 авг. 2018 г. в 17:27, Alan Stern :
>>
>> On Fri, 10 Aug 2018, Laurent Pinchart wrote:
>>
>> > > > Aren't you're missing a dma_sync_single_for_device() call before
>> > > > submitting the URB ? IIRC that's required for correct operation of the
On Sunday, August 12, 2018 6:09:30 PM CEST Leo Yan wrote:
> To avoid staying in a shallow state for a long time, the menu governor
> relies on not stopping tick when detects the prediction is shorter than
> the tick event. This is just luckily to cover most cases but cannot say
> it is completely
On 08/20/2018 04:25 PM, Kim Phillips wrote:
On Mon, 20 Aug 2018 15:36:47 +0100
Suzuki K Poulose wrote:
On 08/20/2018 03:22 PM, Kim Phillips wrote:
On Mon, 20 Aug 2018 11:03:03 +0100
Suzuki K Poulose wrote:
On 08/16/2018 08:28 PM, Mathieu Poirier wrote:
On Wed, 15 Aug 2018 at 09:28, Kim Ph
On Mon, Aug 20, 2018 at 05:11:53PM -0500, Brijesh Singh wrote:
> Hi All,
>
> The following commit
>
> "
> x86/kvmclock: Remove memblock dependency
>
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=368a540e0232ad446931f5a4e8a5e06f69f21343
>
> "
> broke the SEV sup
On Sunday, August 12, 2018 6:09:26 PM CEST Leo Yan wrote:
> We found the CPU cannot stay in deepest idle state as expected with
> running synthetic workloads with mainline kernel on Arm platform
> (96boards Hikey620 with octa CA53 CPUs).
>
> The main issue is the criteria for decision stopping tic
Hi Masahiro,
Masahiro Yamada wrote on Tue, 21 Aug
2018 17:23:19 +0900:
> Commit 49aa76b16676 ("mtd: rawnand: do not execute nand_scan_ident()
> if maxchips is zero") gave a new meaning for calling nand_scan_ident()
> with maxchips=0.
>
> It is a special usage for some drivers such as docg4, but
From: Rafael J. Wysocki
The case addressed by commit 5ef499cd571c (cpuidle: menu: Handle
stopped tick more aggressively) in the stopped tick case is present
when the tick has not been stopped yet too. Namely, if only two CPU
idle states, shallow state A with target residency significantly
below
The incomplete report flooded after S3 and touchscreen becomes
malfunctioned.
[ 1367.646244] i2c_hid i2c-CUST:00: i2c_hid_get_input: incomplete report
(58/18785)
[ 1367.649471] i2c_hid i2c-CUST:00: i2c_hid_get_input: incomplete report
(58/28743)
[ 1367.651092] i2c_hid i2c-CUST:00: i2c
On 20.08.2018 18:03, Cornelia Huck wrote:
> On Mon, 13 Aug 2018 17:48:19 -0400
> Tony Krowiak wrote:
>
>> From: Tony Krowiak
>>
>> This patch provides documentation describing the AP architecture and
>> design concepts behind the virtualization of AP devices. It also
>> includes an example of how
Hi Rahul,
On 04/07/18 17:57, Rahul Ramasubramanian wrote:
Measuring DDR bandwidth allows for an accurate measurement
of memory throughput achieved for a given workload. It also
breaks down the traffic measurement on a per DDR channel basis.
The commit description doesn't help much for someone
Hi Boris,
> -Original Message-
> From: Boris Brezillon [mailto:boris.brezil...@bootlin.com]
> Sent: Tuesday, August 21, 2018 11:30 AM
> To: Naga Sureshkumar Relli
> Cc: miquel.ray...@bootlin.com; rich...@nod.at; dw...@infradead.org;
> computersforpe...@gmail.com; marek.va...@gmail.com; ky
Hi,
Here are patches to remove BUG_ON from kprobes.
Since BUG_ON() kills the machine, it must not be used
for debugging or assertion. These patches remove
meaningless BUG_ON or replace it with return errors.
Thank you,
---
Masami Hiramatsu (5):
kprobes: Remove meaningless BUG_ON from dis
All aggr_probe at this line are already disarmed by
disable_kprobe() or checked by kprobe_disarmed().
So this BUG_ON() does meaningless check. Remove it.
Signed-off-by: Masami Hiramatsu
---
kernel/kprobes.c |1 -
1 file changed, 1 deletion(-)
diff --git a/kernel/kprobes.c b/kernel/kprobes.c
Before calling add_new_kprobe(), aggr_probe's GONE
flag and kprobe GONE flag are cleared. We don't need
to worry about that flag at this point.
Signed-off-by: Masami Hiramatsu
---
kernel/kprobes.c |2 --
1 file changed, 2 deletions(-)
diff --git a/kernel/kprobes.c b/kernel/kprobes.c
index d
Since reuse_unused_kprobe is called when the given kprobe
is unused, checking it inside again with BUG_ON is
meaningless. Remove it.
Signed-off-by: Masami Hiramatsu
---
kernel/kprobes.c |1 -
1 file changed, 1 deletion(-)
diff --git a/kernel/kprobes.c b/kernel/kprobes.c
index 231569e1e2c8..
Make reuse_unused_kprobe() to return error code if
it fails to reuse unused kprobe for optprobe instead
of calling BUG_ON().
Signed-off-by: Masami Hiramatsu
---
kernel/kprobes.c | 27 ---
1 file changed, 20 insertions(+), 7 deletions(-)
diff --git a/kernel/kprobes.c b/
Instead of calling BUG_ON, if we find a kprobe in use on free kprobe
list, just remove it from the list and keep it on kprobe hash list
as same as other in-use kprobes.
Signed-off-by: Masami Hiramatsu
---
kernel/kprobes.c |8 +++-
1 file changed, 7 insertions(+), 1 deletion(-)
diff --gi
Looks good. Thanks.
regards,
dan carpenter
Great. Thanks!
regards,
dan carpenter
(+CC Rob, DT, LKML)
I forgot to CC this to DT community...
2018-08-21 18:30 GMT+09:00 Masahiro Yamada :
> The MIO DMAC (Media IO DMA Controller) is used in UniPhier LD4,
> Pro4, and sLD8 SoCs.
>
> Signed-off-by: Masahiro Yamada
> ---
>
> .../devicetree/bindings/dma/uniphier-mio-dmac.txt | 28
Hello.
Please pull h8300 update.
The following changes since commit 94710cac0ef4ee177a63b5227664b38c95bbf703:
Linux 4.18 (2018-08-12 13:41:04 -0700)
are available in the git repository at:
git://git.sourceforge.jp/gitroot/uclinux-h8/linux.git
for you to fetch changes up to 724d2da5ebca23
Hi Rasmus,
On (08/21/18 09:59), Rasmus Villemoes wrote:
> > +char *sysfs_strncpy(char *dest, const char *src, size_t count)
> > +{
> > + char *c;
> > +
> > + strncpy(dest, skip_spaces(src), count);
>
> I'd like to see where and how you'd use this, but I'm very skeptical of
> count being used
(+CC LKML just in case)
2018-08-21 18:30 GMT+09:00 Masahiro Yamada :
> The MIO DMAC (Media IO DMA Controller) is used in UniPhier LD4,
> Pro4, and sLD8 SoCs.
>
> Signed-off-by: Masahiro Yamada
> ---
>
> MAINTAINERS | 1 +
> drivers/dma/Kconfig | 11 +
> drivers/dma/M
Hi Naga,
Naga Sureshkumar Relli wrote on Tue, 21 Aug 2018
09:22:07 +:
> Hi Boris,
>
> > -Original Message-
> > From: Boris Brezillon [mailto:boris.brezil...@bootlin.com]
> > Sent: Tuesday, August 21, 2018 11:30 AM
> > To: Naga Sureshkumar Relli
> > Cc: miquel.ray...@bootlin.com; ri
Hi Al,
Can you add these patches to the mount API stuff?
There are some fixes and some adjustments to the code.
The patches can also be found here:
http://git.kernel.org/cgit/linux/kernel/git/dhowells/linux-fs.git/log/?h=mount-api-2
Thanks,
David
---
Andrei Vagin (1):
proc: Se
vfs_dup_fs_context() allocates the wrong type of structure and as a result
ends up with one that's too small.
This isn't a problem at this time as nothing uses vfs_dup_fs_context() yet
(until nfs and btrfs conversions come along).
Fixes: ad3e21240b41 ("vfs: Implement a filesystem superblock
crea
On (08/21/18 18:50), Sergey Senozhatsky wrote:
>
> Going point, that's why the patch is in RFC stage: to figure out
> what do we actually want.
s/Going/Good/ don't know how did that happen.
-ss
If an fs_context-based mount is called from mount(2) or some other place
that doesn't set up the logging-through-fd, then under some circumstances
an oops will occur due to the log being unconditionally accessed in
logfc().
Fix this by checking whether there is a log structure before attempting to
Move the source fs parameter to the first position in the parameter list,
numerically speaking. Note that it isn't moved in the key string table as
that's a sorted list.
Signed-off-by: David Howells
---
fs/afs/super.c | 20 ++--
1 file changed, 10 insertions(+), 10 deletions(
Adjust the output of the test-fsinfo sample program to:
(1) Print server addresses if of AF_INET or AF_INET6 family.
(2) Not print parameter descriptions (the test-fs-query sample program can
be used for that).
(3) Only print non-blank parameter values so that parameters that just
e
Pass the path, not just the dentry, into the superblock get_fsinfo
operation because s->s_root isn't useful on NFS for retrocalculating the
source name, but rather mnt->mnt_root must be used.
Further, rename the ->get_fsinfo() superblock op to ->fsinfo() for
consistency.
Signed-off-by: David Howe
From: Andrei Vagin
Fix the setting up a new proc superblock for a new pid_namespace such that
the user_ns for that proc superblock needs to be taken from the new
pid_namespace and not the active process.
Signed-off-by: Andrei Vagin
Signed-off-by: David Howells
---
fs/proc/root.c |5 +
On Mon, 2018-08-20 at 15:27 -0700, Linus Torvalds wrote:
> On Mon, Aug 20, 2018 at 3:02 PM Woodhouse, David wrote:
> >
> > It's the *kernel* we don't want being able to access those pages,
> > because of the multitude of unfixable cache load gadgets.
>
> Ahh.
>
> I guess the proof is in the pudd
On Tue, Aug 07, 2018 at 02:02:35PM +0200, Miklos Szeredi wrote:
> On Fri, Jun 29, 2018 at 2:53 PM, Niels de Vos wrote:
> > There are several FUSE filesystems that can implement server-side copy
> > or other efficient copy/duplication/clone methods. The copy_file_range()
> > syscall is the standard
The patch 623a6143a845("mailbox: mediatek: Add Mediatek CMDQ driver")
introduce the following static checker warning:
drivers/mailbox/mtk-cmdq-mailbox.c:366 cmdq_mbox_send_data()
error: potential null dereference 'task'. (kzalloc returns null)
Fixes: 623a6143a845 ("mailbox: mediatek: Add Medi
On Tue, 2018-08-21 at 15:48 +0900, Masahiro Yamada wrote:
> Commit cafa0010cd51 ("Raise the minimum required gcc version to 4.6")
> missed the fact that is included by Clang
> as well as by GCC.
>
> Clang actually defines __GNUC__, __GNUC_MINOR__, __GNUC_PATCHLEVEL__
> and it looks like GCC 4.2.1
On 21 August 2018 at 15:17, Masahiro Yamada
wrote:
> (+CC Rob, DT, LKML)
>
> I forgot to CC this to DT community...
>
>
> 2018-08-21 18:30 GMT+09:00 Masahiro Yamada :
>> The MIO DMAC (Media IO DMA Controller) is used in UniPhier LD4,
>> Pro4, and sLD8 SoCs.
>>
>> Signed-off-by: Masahiro Yamada
>>
device_online() should be called with device_hotplug_lock() held.
Cc: Benjamin Herrenschmidt
Cc: Paul Mackerras
Cc: Michael Ellerman
Cc: Rashmica Gupta
Cc: Balbir Singh
Cc: Michael Neuling
Signed-off-by: David Hildenbrand
---
arch/powerpc/platforms/powernv/memtrace.c | 2 ++
1 file changed
This is the same approach as in the first RFC, but this time without
exporting device_hotplug_lock (requested by Greg) and with some more
details and documentation regarding locking. Tested only on x86 so far.
--
Reading thro
Hi Miquel,
> -Original Message-
> From: Miquel Raynal [mailto:miquel.ray...@bootlin.com]
> Sent: Tuesday, August 21, 2018 3:23 PM
> To: Naga Sureshkumar Relli
> Cc: Boris Brezillon ; rich...@nod.at;
> dw...@infradead.org;
> computersforpe...@gmail.com; marek.va...@gmail.com; kyungmin.p..
On 20/08/2018 23:37, Arnd Bergmann wrote:
> Removing one of the two accesses of the maxphyaddr variable led to
> a harmless warning:
>
> arch/x86/kvm/x86.c: In function 'kvm_set_mmio_spte_mask':
> arch/x86/kvm/x86.c:6563:6: error: unused variable 'maxphyaddr'
> [-Werror=unused-variable]
>
> Remo
On Tue, 21 Aug 2018 10:44:54 +
Naga Sureshkumar Relli wrote:
> Hi Miquel,
>
> > -Original Message-
> > From: Miquel Raynal [mailto:miquel.ray...@bootlin.com]
> > Sent: Tuesday, August 21, 2018 3:23 PM
> > To: Naga Sureshkumar Relli
> > Cc: Boris Brezillon ; rich...@nod.at;
> > dw..
On 2018-08-21 16:13, Borislav Petkov wrote:
On Mon, Aug 20, 2018 at 12:14:58AM +0800, Pu Wen wrote:
...
diff --git a/drivers/edac/amd64_edac.c b/drivers/edac/amd64_edac.c
index 18aeabb..3cefb25 100644
--- a/drivers/edac/amd64_edac.c
+++ b/drivers/edac/amd64_edac.c
@@ -211,7 +211,8 @@ static int
On Tue, 21 Aug 2018 09:22:07 +
Naga Sureshkumar Relli wrote:
> Hi Boris,
>
> > -Original Message-
> > From: Boris Brezillon [mailto:boris.brezil...@bootlin.com]
> > Sent: Tuesday, August 21, 2018 11:30 AM
> > To: Naga Sureshkumar Relli
> > Cc: miquel.ray...@bootlin.com; rich...@nod.
On Tue, 2018-08-21 at 15:11 +1000, NeilBrown wrote:
> On Thu, Aug 16 2018, NeilBrown wrote:
>
> > On Wed, Aug 15 2018, Jeff Layton wrote:
> >
> > > On Wed, 2018-08-15 at 14:28 +0200, Krzysztof Kozlowski wrote:
> > > > Hi,
> > > >
> > > > Bisect pointed commit ce3147990450a68b3f549088b30f087742a0
On Tue, Aug 21, 2018 at 07:04:23PM +0800, Pu Wen wrote:
> Sure, JV will negotiate with AMD and make sure only JV use family 18h and
> AMD won't use family 0x18h, which will make the patch tight and clear.
>
> What's the best way to adapt for EDAC driver?
> * To simplify the code based on AMD won't
On 21/08/2018 13:20, Borislav Petkov wrote:
> On Tue, Aug 21, 2018 at 07:04:23PM +0800, Pu Wen wrote:
>> Sure, JV will negotiate with AMD and make sure only JV use family 18h and
>> AMD won't use family 0x18h, which will make the patch tight and clear.
>>
>> What's the best way to adapt for EDAC dr
Hello Stephen,
Thanks for the changes, I have tested the changes and would require the
change mentioned below for this to work.
On 8/18/2018 11:31 PM, Taniya Das wrote:
Hello Stephen,
I will test these changes and get back.
On 8/18/2018 7:42 AM, Stephen Boyd wrote:
Quoting Taniya Das (2018
From: Colin Ian King
Currently the return from get_user_pages_fast is being checked
to be less than zero for an error check, however, the variable being
checked is unsigned so the check is always false. Fix this by using
a signed long instead.
Detected by Coccinelle ("Unsigned expression compare
On (08/21/18 18:50), Sergey Senozhatsky wrote:
>
> > int strcpy_trim(char *dst, size_t dstsize, const char *src, size_t
> > srcsize) - copy (potentially not '\0'-terminated) src to dst, trimming
> > leading and trailing whitespace. dstsize must be positive, and dst is
> > guaranteed to be '\0'-ter
On 08/21/2018 01:04 PM, Naveen N. Rao wrote:
> Song Liu wrote:
>> I am testing the patch set with the following code:
>>
>> #include
>> #include
>>
>> volatile short semaphore = 0;
>>
>> int for_uprobe(int c)
>> {
>> printf("%d\n", c + 10);
>> return c + 1;
>> }
>>
>> int main(i
On Tue, 2018-08-21 at 20:44 +0900, Sergey Senozhatsky wrote:
> Something like below? Not tested, since we are still in "is this
> what we want" phase.
> Returning the length of dst/-EOVERFLOW is a bit inconvenient, because
> "the length" forces us to have size_t return, which is unsigned.
We hav
* Srikar Dronamraju [2018-08-03 11:43:55]:
> This patchset based on current tip/sched/core, provides left out patches
> from the previous series. This version handles the comments given to some of
> the patches. It drops "sched/numa: Restrict migrating in parallel to the same
> node." It adds an
The strncpy doesn't null terminate the string because the size is too
short by one byte.
parse.c: In function ‘prepare_default_config’:
parse.c:148:2: warning: ‘strncpy’ output truncated before terminating
nul copying 8 bytes from a string of the same length
[-Wstringop-truncation]
strnc
On Mon 20-08-18 14:24:40, Andrew Morton wrote:
> On Mon, 20 Aug 2018 10:55:16 +0200 Oscar Salvador
> wrote:
>
> > From: Oscar Salvador
> >
> > Currently, NODEMASK_ALLOC allocates a nodemask_t with kmalloc when
> > NODES_SHIFT is higher than 8, otherwise it declares it within the stack.
> >
>
Hi,
Thanks a lot for the review ! I just have a question below regarding
populate method.
Le 07/10/2018 12:38 AM, Enric Balletbo Serra a écrit :
> Hi Pascal,
>
> Thanks for the patch some comments below.
>
> Missatge de Pascal PAILLET-LME del dia dj., 5 de
> jul. 2018 a les 17:17:
>> From: pas
On Tue, Aug 21, 2018 at 11:36:34AM +, Colin King wrote:
> From: Colin Ian King
>
> Currently the return from get_user_pages_fast is being checked
> to be less than zero for an error check, however, the variable being
> checked is unsigned so the check is always false. Fix this by using
> a si
On Tue, Aug 21, 2018 at 02:17:34PM +0200, Michal Hocko wrote:
> We do have CONFIG_NODES_SHIFT=10 in our SLES kernels for quite some
> time (around SLE11-SP3 AFAICS).
>
> Anyway, isn't NODES_ALLOC over engineered a bit? Does actually even do
> larger than 1024 NUMA nodes? This would be 128B and fro
There are several FUSE filesystems that can implement server-side copy
or other efficient copy/duplication/clone methods. The copy_file_range()
syscall is the standard interface that users have access to while not
depending on external libraries that bypass FUSE.
Signed-off-by: Niels de Vos
---
Previously, the CGU code corresponding to the SoC for which we're
compiling the kernel was the only one enabled, which made it impossible
to build one kernel that supports them all.
Now, it is possible to select more than one SoC to support.
Signed-off-by: Paul Cercueil
---
drivers/clk/Kconfig
Add support for the clocks provided by the CGU in the Ingenic JZ4725B
SoC.
Signed-off-by: Paul Cercueil
---
drivers/clk/ingenic/Kconfig | 10 ++
drivers/clk/ingenic/Makefile | 1 +
drivers/clk/ingenic/jz4725b-cgu.c | 225 ++
3 files changed, 236 insertio
Hi Tejun, Lia, all,
While doing some unrelated testing earlier, I found a bug in workqueue
lockdep, and while looking into the code I found another bug, and another
limitation. I'll follow up with patches for the two bugs, and explain all
three issues here.
1)
Lockdep report is below - the pro
1 - 100 of 410 matches
Mail list logo
