On 2 September 2018 at 09:30, Andreas Kemnade wrote:
> after unbinding mmc I get things like this:
> [ 185.294067] mmc1: card 0001 removed
> [ 185.305206] omap_hsmmc 480b4000.mmc: wake IRQ with no resume: -13
>
> The wakeirq stays in /proc-interrupts
>
> rebinding shows this:
> [ 289.795959]
On 4 September 2018 at 04:59, YueHaibing wrote:
> Fix inconsistent IS_ERR and PTR_ERR in tegra_sdhci_init_pinctrl_info,
> the proper pointer to be passed as argument is 'pinctrl_state_1v8'
>
> Signed-off-by: YueHaibing
Thanks, applied for next!
Kind regards
Uffe
> ---
>
Em Tue, Sep 04, 2018 at 04:17:24PM +0200, Peter Zijlstra escreveu:
> On Tue, Sep 04, 2018 at 10:42:18AM -0300, Arnaldo Carvalho de Melo wrote:
> > Then I need to get the DW_AT_location stuff parsed in pahole, so
> > that with those offsets (second column, ending with :) with hits (first
> >
This change adds the ttyAML1 uart used by the brmcfmac sdio module in
the WeTek Hub and WeTek Play 2 devices.
Signed-off-by: chewitt
---
arch/arm64/boot/dts/amlogic/meson-gxbb-wetek.dtsi | 8
1 file changed, 8 insertions(+)
diff --git
On 09/04/2018 09:55 AM, Mark Brown wrote:
> On Tue, Sep 04, 2018 at 09:43:03AM -0500, Andrew F. Davis wrote:
>> On 09/04/2018 09:41 AM, Mark Brown wrote:
>
> If we really want to pay attention to something setting this up we'd
> need to completely remove the widget - what the code is
On Tue, Sep 04, 2018 at 07:54:51AM -0700, Sean Christopherson wrote:
> I don't see any value in trying to rule out specific causes of
> INVALID_TOKEN, but we should only retry EINIT if ret==INVALID_TOKEN
> and RDMSR(HASH0) != sgx_lepubkeyhash[0]. Only the first MSR needs to
> be checked for
not apply cleanly.
drivers/regulator/core.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--- linux-next-20180904.orig/drivers/regulator/core.c
+++ linux-next-20180904/drivers/regulator/core.c
@@ -4466,7 +4466,7 @@ EXPORT_SYMBOL_GPL(regulator_unregister);
#ifdef CONFIG_SUSPEND
On Tue, Sep 4, 2018 at 12:28 PM, Alex Gonzalez wrote:
> + {
> + pinctrl-names = "default";
> + pinctrl-0 = <_lcdif_dat0_17
> +_lcdif_clken
> +_lcdif_hvsync>;
> + lcd-supply = <_ext>; /* BU90T82 LVDS bridge power */
> + status
From: Colin Ian King
Don't populate the array 'broadcast' on the stack but instead make it
static. Makes the object code smaller by 53 bytes:
Before:
textdata bss dec hex filename
105111521 448 1248030c0 drivers/staging/most/net/net.o
After:
textdata
To prevent warning "kernfs: can not remove '(null)', no directory" if an
overlay isn't applied to the active devicetree.
Using of_remove_property and then of_add_property doesn't show the warning.
Signed-off-by: Andre Kalb
---
Changes in v2:
- Fix typo
drivers/of/kobj.c | 2 +-
1 file
On Mon, 27 Aug 2018 05:47:21 -0700
Li Qiang wrote:
> Free the vdev->msi_perm in error path.
>
> Signed-off-by: Li Qiang
> ---
> drivers/vfio/pci/vfio_pci_config.c | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/vfio/pci/vfio_pci_config.c
>
On Tue, Sep 04, 2018 at 10:36:18AM -0500, Andrew F. Davis wrote:
> This device can detect the insertion/removal of headphones and headsets.
> Enable reporting this status by enabling this interrupt and forwarding
> this to upper-layers if a jack has been defined.
This doesn't apply against
On 09/03/2018 06:16 AM, Andy Shevchenko wrote:
>> + EBLOCK = 0x9,
>> + EPA = 0xA,
>> + EWB = 0xB,
>> + ETRACK = 0xC,
>> + EAUG= 0xD,
>> + EMODPR = 0xE,
>> + EMODT = 0xF,
>> +};
> Hmm... This E prefix confuses me with (system wide) error
'error' variable is left uninitialized in case we see an unknown operation.
As we don't immediately return and proceed to pwrite() we need to set it
to something, HV_E_FAIL sounds good enough.
Signed-off-by: Vitaly Kuznetsov
---
tools/hv/hv_fcopy_daemon.c | 1 +
1 file changed, 1 insertion(+)
On Tue, Sep 04, 2018 at 11:45:02PM +0800, Pu Wen wrote:
> I add these definitions to indicate that there are Hygon PCI device IDs.
> You are right, I can just use the AMD f17h ones here.
Right, if this is a small piece where they're all together in a single
compilation unit - like in this case -
From: Jay Kamat
Add tests for memory.oom.group for the following cases:
- Killing all processes in a leaf cgroup, but leaving the
parent untouched
- Killing all processes in a parent and leaf cgroup
- Keeping processes marked by OOM_SCORE_ADJ_MIN alive when considered
for being killed by the
From: Jay Kamat
Fix a couple issues with cg_read_strcmp(), to improve correctness of
cgroup tests
- Fix cg_read_strcmp() always returning 0 for empty "needle" strings
- Fix a memory leak in cg_read_strcmp()
Fixes: 84092dbcf901 ("selftests: cgroup: add memory controller self-tests")
Hi Shuah,
I wrote some tests for the new memory.oom.group feature in cgroups 2.
In the process, I discovered a few small bugs in the cgroups tests, which
I have fixed as well in a separate commit.
This is my first ever patch to Linux, so let me know if you see any issues or
improvements that
In noirq suspend/resume stage with no_console_suspend enabled,
imx_uart_console_write() may be called to print out log_buf
message by printk(), so there will be race condition between
imx_uart_console_write() and imx_uart_save/restore_context(),
need to add lock to protect the registers
On some i.MX SoCs' low power mode, such as i.MX7D's LPSR(low power
state retention), UART iomux settings will be lost, need to add
pinctrl sleep/default mode switch during suspend/resume to make
sure UART iomux settings are correct after resume.
Signed-off-by: Anson Huang
---
On Fri, 31 Aug 2018 15:17:44 +
Matteo Croce wrote:
> On Fri, Aug 31, 2018 at 3:49 AM Nicholas Piggin wrote:
> >
> > On Tue, 28 Aug 2018 15:00:14 +
> > Matteo Croce wrote:
> >
> > > On Tue, Aug 28, 2018 at 2:35 PM Nicholas Piggin
> > > wrote:
> > > >
> > > > On Tue, 28 Aug 2018
Currently, broadcast base is set to end of the LLCC banks, which may
not be correct always. As the number of banks may vary for each chipset
and the broadcast base could be at a different address as well. This info
depends on the chipset, so get the broadcast base info from the device
tree (DT).
Add reg-names and interrupts for LLCC documentation and the usage
examples. llcc broadcast base is added in addition to llcc base,
which is used for llcc broadcast writes.
Signed-off-by: Venkata Narendra Kumar Gutta
Reviewed-by: Rob Herring
---
.../devicetree/bindings/arm/msm/qcom,llcc.txt
Cache error reporting controller detects and reports single and
double bit errors on Last Level Cache Controller (LLCC) cache.
Add required support to register LLCC EDAC driver as platform driver,
from LLCC driver.
Signed-off-by: Venkata Narendra Kumar Gutta
Reviewed-by: Evan Green
---
From: Channagoud Kadabi
Add error reporting driver for Single Bit Errors (SBEs) and Double Bit
Errors (DBEs). As of now, this driver supports error reporting for
Last Level Cache Controller (LLCC) of Tag RAM and Data RAM. Interrupts
are triggered when the errors happen in the cache, the driver
This series implements EDAC driver for QCOM SoCs. As of now, this driver
supports EDAC for Last Level Cache Controller (LLCC). LLCC EDAC driver is
to detect and report single and double bit errors on Last Level Cache
Controller (LLCC) cache. Interrupts are triggered when the errors happen
in the
Hi all,
On Tue, 4 Sep 2018 15:54:27 +0530 Amit Kucheria
wrote:
>
> I'm currently reviewing this patchset (long overdue), but considering
> that we haven't added any major new features to the framework for the
> last couple of revisions, can you get this patchset merged into
> linux-next to see
Hi, Uwe
Anson Huang
Best Regards!
> -Original Message-
> From: Uwe Kleine-König
> Sent: Wednesday, September 5, 2018 4:32 AM
> To: Anson Huang
> Cc: gre...@linuxfoundation.org; jsl...@suse.com;
> linux-ser...@vger.kernel.org; linux-kernel@vger.kernel.org; dl-linux-imx
>
> Subject:
On 08/30/18 12:05, Rob Herring wrote:
> Now that we initialize dt_root_addr_cells and dt_root_size_cells earlier,
> use them and simplify of_fdt_limit_memory.
>
> Cc: Frank Rowand
> Signed-off-by: Rob Herring
> ---
> drivers/of/fdt.c | 23 +--
> 1 file changed, 1
Hi all,
On Wed, 5 Sep 2018 10:39:06 +1000 Stephen Rothwell
wrote:
>
> After merging the devicetree tree, today's linux-next build (x86_64
> allmodconfig) produced these warnings:
>
> WARNING: vmlinux.o(.text+0xf40a16): Section mismatch in reference from the
> function of_fdt_limit_memory() to
Hi Jacek,
On 5 September 2018 at 04:19, Jacek Anaszewski
wrote:
> Hi Baolin,
>
> On 09/04/2018 01:01 PM, Baolin Wang wrote:
>> This patch implements the 'pattern_set'and 'pattern_clear'
>> interfaces to support SC27XX LED breathing mode.
>>
>> Signed-off-by: Baolin Wang
>> ---
>> Changes from
On 09/04/2018 02:54 PM, Thomas Gleixner wrote:
On Thu, 30 Aug 2018, subhra mazumdar wrote:
+void pipe_busy_wait(struct pipe_inode_info *pipe)
+{
+ unsigned long wait_flag = pipe->pipe_wait_flag;
+ unsigned long start_time = pipe_busy_loop_current_time();
+
+
Hi Rob,
After merging the devicetree tree, today's linux-next build (x86_64
allmodconfig) produced these warnings:
WARNING: vmlinux.o(.text+0xf40a16): Section mismatch in reference from the
function of_fdt_limit_memory() to the variable .init.data:dt_root_addr_cells
The function
> -Original Message-
> From: Andrea Arcangeli [mailto:aarca...@redhat.com]
> Sent: Tuesday, September 04, 2018 4:37 PM
> To: Schaufler, Casey
> Cc: Jiri Kosina ; Tim Chen ;
> Thomas Gleixner ; Ingo Molnar ;
> Peter Zijlstra ; Josh Poimboeuf
> ; Woodhouse, David ; Oleg
> Nesterov ;
On 08/30/18 12:05, Rob Herring wrote:
> Scan the root node properties (#{size,address}-cells) earlier,
^^^
before mdesc->dt_fixup() is called
> so that
> the dt_root_addr_cells and dt_root_size_cells
On 08/30/18 12:05, Rob Herring wrote:
> This is a small restructuring and clean-up of handling root node
> #size-cells and #address-cells (or lack of). As only Sparc needs a
> different default value and only for #address-cells, we can handle that
> locally and remove one more dependency on
Srinivas Pandruvada writes:
> On Mon, 2018-09-03 at 23:53 -0700, Francisco Jerez wrote:
>> Eero Tamminen writes:
>>
>> > Hi,
>> >
>> > On 31.08.2018 20:28, Srinivas Pandruvada wrote:
>> > ...
>> > > As per testing Eero Tamminen, the results are comparable to the
>> > > patchset
>> > >
On 08/30/18 12:05, Rob Herring wrote:
> Only some old OpenFirmware implementations rely on default sizes. Any
> FDT and modern implementation should have explicit properties. Make the
> OF_ROOT_NODE_*_CELLS_DEFAULT defines private so we don't get any outside
> users.
>
> This also gets us one
On Wed, Sep 05, 2018 at 01:00:37AM +, Schaufler, Casey wrote:
> Sorry, I've been working in security too long for my
> optimistic streak to be very wide.
Eheh. So I was simply trying to follow in context, but it wasn't
entirely clear, so I tried to take it out of context and then it was
even
Update .gitignore files.
Signed-off-by: Lei Yang
---
tools/testing/selftests/cgroup/.gitignore | 1 +
1 file changed, 1 insertion(+)
diff --git a/tools/testing/selftests/cgroup/.gitignore
b/tools/testing/selftests/cgroup/.gitignore
index 95eb3a5..adacda5 100644
---
add config file
Signed-off-by: Lei Yang
---
tools/testing/selftests/efivarfs/config | 1 +
1 file changed, 1 insertion(+)
create mode 100644 tools/testing/selftests/efivarfs/config
diff --git a/tools/testing/selftests/efivarfs/config
b/tools/testing/selftests/efivarfs/config
new file mode
Hi Linus,
The following changes since commit 57361846b52bc686112da6ca5368d11210796804:
Linux 4.19-rc2 (2018-09-02 14:37:30 -0700)
are available in the Git repository at:
ssh://g...@gitolite.kernel.org/pub/scm/linux/kernel/git/greentime/linux.git
tags/nds32-for-linus-4.19-tag1
for you to
On 08/30/18 11:52, Rob Herring wrote:
> In preparation to remove direct access to device_node.type, add
> of_node_is_type() and of_node_get_device_type() helpers to check and
> retrieve the device type.
>
> Cc: Frank Rowand
> Signed-off-by: Rob Herring
> ---
> include/linux/of.h | 12
On 09/04/2018 11:48 AM, Jiri Kosina wrote:
> On Tue, 4 Sep 2018, Schaufler, Casey wrote:
>
>>> So if this should be done in LSM, it'd probably have to be written by
>>> someone else than me :) who actually understands how the "sidechannel LSM"
>>> idea works.
>>
>> Yes. That would be me.
>
>
Hello,
On Tue, Sep 04, 2018 at 06:10:47PM +, Schaufler, Casey wrote:
> The real reason to use an LSM based approach is that overloading ptrace
> checks is a Really Bad Idea. Ptrace is a user interface. Side-channel is a
> processor interface. Even if ptrace_may_access() does exactly what you
Hi Stefan,
On Tue, 4 Sep 2018 22:07:15 +0200 (CEST) Stefan Wahren
wrote:
>
> > Eric Anholt hat am 4. September 2018 um 19:41 geschrieben:
> >
> > Stephen Rothwell writes:
> >
> > > Fetching the bcm2835 tree (git://github.com/anholt/linux.git#for-next)
> > > produces this error:
> > >
> >
On Fri, Aug 24, 2018 at 12:42 AM, Martin Schwidefsky
wrote:
> Harald Freudenberger (5):
> s390/zcrypt: hex string mask improvements for apmask and aqmask.
This (and an earlier 2017 commit) adds VLAs, which are being
removed[1] from the kernel:
drivers/s390/crypto/ap_bus.c:980:3: warning:
On Tue, Sep 04, 2018 at 01:35:34PM -0700, Vito Caputo wrote:
> On Tue, Sep 04, 2018 at 04:18:18PM -0400, Jeff Layton wrote:
> > On Tue, 2018-09-04 at 14:54 -0400, J. Bruce Fields wrote:
> > > On Tue, Sep 04, 2018 at 06:23:48PM +0200, Rogier Wolff wrote:
> > > > On Tue, Sep 04, 2018 at 12:12:03PM
On 08/31/2018 09:09 AM, Steven Sistare wrote:
On 8/30/2018 4:24 PM, subhra mazumdar wrote:
Introduce pipe_ll_usec field for pipes that indicates the amount of micro
seconds a thread should spin if pipe is empty or full before sleeping. This
is similar to network sockets. Workloads like
It uses modprobe $TEST_DRIVER in sysctl.sh, so update
config to use "m" instead
Signed-off-by: Lei Yang
---
tools/testing/selftests/sysctl/config | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tools/testing/selftests/sysctl/config
b/tools/testing/selftests/sysctl/config
Some leds on our board are active low leds, which means these leds
are lighted when the corresponding gpio line is low, while the
original leds-gpio driver default all leds are active high leds.
This patch adds a devicetree node "light-state", whose value should
be "high" for active high leds and
Hi,
On (09/04/18 20:01), Hans de Goede wrote:
> Commit 375899cddcbb ("printk: make sure to print log on console."), moved
> the checking of the loglevel of messages from flush time to the actual
> log time.
>
> This introduces one problem, some early boot messages are printed before
>
On 08/30/18 11:52, Rob Herring wrote:
> In preparation to remove device_node.name pointer, add helper functions
> for node name comparisons which are a common pattern throughout the kernel.
>
> Cc: Frank Rowand
> Signed-off-by: Rob Herring
> ---
> drivers/of/base.c | 22 ++
On 2018-08-30 05:11, Borislav Petkov wrote:
On Tue, Aug 28, 2018 at 05:42:26PM -0700, Venkata Narendra Kumar Gutta
wrote:
From: Channagoud Kadabi
Add error reporting driver for Single Bit Errors (SBEs) and Double Bit
Errors (DBEs). As of now, this driver supports error reporting for
Last
Hi,
On Mon, Sep 3, 2018 at 1:34 PM, Bjorn Andersson
wrote:
> On Tue 28 Aug 06:38 PDT 2018, Amit Kucheria wrote:
>
>> Instead of showing up as thermal-sensor@, the nodes will show up as
>> tsens0_tm, tsen1_tm, tsens1_srot, etc. in /proc/iomem making it easier to
>> read.
>>
>> IOW,
>>
>>
In resctrl filesystem, we have some mount options to enable
L3/L2 CDP and MBA Software Controller features if platform supports them:
mount -t resctrl resctrl [-o cdp[,cdpl2][,mba_MBps]] /sys/fs/resctrl
But currently only "cdp" option can be displayed. "cdpl2" and "mba_MBps"
options are not
On Thu, Aug 30, 2018 at 12:47:27PM -0700, Eric Biggers wrote:
> From: Eric Biggers
>
> This simplifies the code. No change in behavior.
>
> Signed-off-by: Eric Biggers
> ---
> lib/parser.c | 5 +
> 1 file changed, 1 insertion(+), 4 deletions(-)
>
> diff --git a/lib/parser.c
This series adds PCIe host controller driver for Socionext UniPhier SoCs.
This controller is based on the DesignWare PCIe core. This driver
supports LD20 and PXs3 SoCs.
Kunihiko Hayashi (2):
dt-bindings: pci: add UniPhier PCIe host controller description
pci: dwc: add UniPhier PCIe host
This introduces specific glue layer for UniPhier platform to support
PCIe host controller that is based on the Designware PCIe Core, and
this driver supports Root Complex (host) mode.
Signed-off-by: Kunihiko Hayashi
---
drivers/pci/controller/dwc/Kconfig | 9 +
Add DT bindings for PCIe controller implemented in UniPhier SoCs when
configured in Root Complex (host) mode. This controller is based on
the Designware PCIe Core.
Signed-off-by: Kunihiko Hayashi
---
.../devicetree/bindings/pci/uniphier-pcie.txt | 78 ++
1 file changed,
sorry, the title should be :"cgroup: kselftests: add test_core to
.gitignore"
Lei
On 2018年09月05日 10:39, Lei Yang wrote:
Update .gitignore files.
Signed-off-by: Lei Yang
---
tools/testing/selftests/cgroup/.gitignore | 1 +
1 file changed, 1 insertion(+)
diff --git
Hi all,
Changes since 20180904:
Dropped trees: xarray, ida (temporarily)
The net-next tree still had its build failure for which I reverted
a commit.
The devicetree tree gained a build failure for which I applied a patch.
Non-merge commits (relative to Linus' tree): 1853
2252 files changed
Hi,
On Tue, 4 Sep 2018 16:34:56 +0200
Ulf Hansson wrote:
> On 2 September 2018 at 09:30, Andreas Kemnade wrote:
> > after unbinding mmc I get things like this:
> > [ 185.294067] mmc1: card 0001 removed
> > [ 185.305206] omap_hsmmc 480b4000.mmc: wake IRQ with no resume: -13
> >
> > The
On Thu, Aug 09, 2018 at 06:06:09PM +0800, Anson Huang wrote:
> On some i.MX SoCs' low power mode, UART iomux settings
Would be nice to point out specific affected SoCs.
> may be lost, need to add pinctrl sleep/default mode switch
> during suspend/resume to make sure UART iomux settings are
>
On 8/31/2018 12:20 PM, Florian Fainelli wrote:
Enable the SFP connected to port 5 of the switch and wire up all GPIOs
to the SFP cage. Because of a hardware limitation of the i2c controller
on the iProc SoCs which prevents large i2c (> 63 bytes) transactions to
work, we use the i2c-gpio
Pavel Tatashin, Ying Huang, and I are excited to be organizing a performance
and scalability microconference this year at Plumbers[*], which is happening in
Vancouver this year. The microconference is scheduled for the morning of the
second day (Wed, Nov 14).
We have a preliminary agenda and
Hi Masahiro,
Masahiro Yamada wrote on Mon, 20 Aug
2018 12:26:36 +0900:
> Use SPDX-License-Identifier instead of the license boilerplates.
>
> This conversion makes it easier for us to scan the license, then
> I notice license mismatch problems.
>
> The license blocks in denali* indicate
On 09/04/2018 01:32 PM, Greg Kroah-Hartman wrote:
> On Tue, Sep 04, 2018 at 09:49:43AM +0530, Naresh Kamboju wrote:
>> On 3 September 2018 at 22:24, Greg Kroah-Hartman
>> wrote:
>>> This is the start of the stable review cycle for the 4.14.68 release.
>>> There are 165 patches in this series, all
On Wed, Sep 05, 2018 at 12:38:22AM +0200, Dominique Martinet wrote:
> The 'm' kcore_list item could point to kclist_head, and it is incorrect to
> look at m->addr / m->size in this case.
> There is no choice but to run through the list of entries for every address
> if we did not find any entry in
Commit 9092c71bb724 ("mm: use sc->priority for slab shrink targets")
changed the way how the target slab pressure is calculated and
made it priority-based:
delta = freeable >> priority;
delta *= 4;
do_div(delta, shrinker->seeks);
The problem is that on a default priority (which is
On Tue, Sep 4, 2018 at 12:25 PM Dave Hansen wrote:
>
> On 09/04/2018 11:33 AM, Alexander Duyck wrote:
> > --- a/mm/memblock.c
> > +++ b/mm/memblock.c
> > @@ -1444,7 +1444,7 @@ void * __init memblock_virt_alloc_try_nid_raw(
> >
> > ptr = memblock_virt_alloc_internal(size, align,
> >
On Tue, 4 Sep 2018 12:45:28 +0100 Will Deacon wrote:
> This series builds on the core changes I previously posted here:
>
> rfc:
> http://lists.infradead.org/pipermail/linux-arm-kernel/2018-August/597821.html
> v1:
>
inet_fill_ifaddr() already took 6 arguments which meant the 7th argument
would need to be pushed onto the stack on x86.
Add a new struct inet_fill_args which holds common information passed
to inet_fill_ifaddr() and shortens the function to three pointer arguments.
Signed-off-by: Christian
On Tue, Sep 04, 2018 at 04:26:11PM -0400, Steven Rostedt wrote:
> On Sat, 1 Sep 2018 21:16:39 -0700
> "Paul E. McKenney" wrote:
>
> > On Sat, Sep 01, 2018 at 06:45:31PM -0400, Steven Rostedt wrote:
> > > On Sat, 1 Sep 2018 10:54:42 -0700
> > > "Paul E. McKenney" wrote:
> > >
> > > > On Sat,
On Tue, Sep 04, 2018 at 01:35:34PM -0700, Vito Caputo wrote:
> Implement a new class of swap space for backing dirty pages which fail
> to write back. Pages in this space survive reboots, essentially backing
> the implicit commitment POSIX establishes in the face of asynchronous
> writeback
On Mon, Aug 27 2018 at 14:01 -0600, Stephen Boyd wrote:
Quoting Lina Iyer (2018-08-24 10:14:32)
On Fri, Aug 24 2018 at 02:22 -0600, Stephen Boyd wrote:
>Quoting Lina Iyer (2018-08-17 12:10:23)
>> During suspend the system may power down some of the system rails. As a
>> result, the TLMM hw
On Tue, Sep 4, 2018 at 2:21 PM, Dave Hansen wrote:
> On 09/04/2018 12:56 PM, Andy Lutomirski wrote:
>> I have no objection to this patch.
>>
>> Dave, why did you think that we could get a PK fault on the vsyscall
>> page, even on kernels that still marked it executable? Sure, you
>> could get an
On Tue, Sep 04, 2018 at 01:35:10PM -0700, Atish Patra wrote:
> sure. How about this ?
That would work, but why not just keep calling sbi_remove_sfence_vma
directly from flush_tlb_all?
On Tue, Sep 04, 2018 at 11:08:35AM -0700, Atish Patra wrote:
>
> I have kept it here to match all other arch. Same goes for all hotplug
> functions in smpboot.c
>
> I can move them to a separate file if you think that provides better code
> readability and structure.
I don't really have a
On 09/04/2018 02:34 PM, Miquel Raynal wrote:
> Hi Randy,
>
> Randy Dunlap wrote on Mon, 3 Sep 2018 12:32:04
> -0700:
>
>> From: Randy Dunlap
>>
>> Fix build warning in by adding a "stub" struct
>> for mtd_oob_ops:
>>
>> include/linux/mtd/onenand.h: warning: 'struct mtd_oob_ops' declared
Hi Michal,
Sorry for the delay in responding. I was traveling last week.
On 08/29/2018 05:08 AM, Michal Hocko wrote:
> On Tue 28-08-18 12:09:53, Shuah Khan wrote:
> [...]
>> The main intent is to use numa emulation in conjunction with cpusets for
>> coarse
>> memory management similar to x86_64
On 09/03/2018 09:48 AM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 4.4.154 release.
There are 80 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.
Responses should be
On 09/03/2018 09:54 AM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 4.14.68 release.
There are 165 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.
Responses should be
On 09/03/2018 09:55 AM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 4.9.125 release.
There are 107 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.
Responses should be
> On 4 Sep 2018, at 11:05 pm, Martin Blumenstingl
> wrote:
>
> Hi Christian,
>
> On Tue, Sep 4, 2018 at 4:47 PM chewitt wrote:
>>
>> This change adds the ttyAML1 uart used by the brmcfmac sdio module in
>> the WeTek Hub and WeTek Play 2 devices.
> do you know which Broadcom chip this is
Hi Alexander,
This is a wrong way to do it. memblock_virt_alloc_try_nid_raw() does not
initialize allocated memory, and by setting memory to all ones in debug
build we ensure that no callers rely on this function to return zeroed
memory just by accident.
And, the accidents are frequent because
As we augmented the regulator core to accept a GPIO descriptor instead
of a GPIO number, we can augment the fixed GPIO regulator to look up
and pass that descriptor directly from device tree or board GPIO
descriptor look up tables.
Some boards just auto-enumerate their fixed regulator platform
Hello,
On Thu, Aug 09, 2018 at 06:06:08PM +0800, Anson Huang wrote:
> In noirq suspend/resume stage with no_console_suspend enabled,
> .imx_console_write() may be called to print out log_buf
> message by .printk(), so there will be race condition between
> .imx_console_write() and
During suspend the system may power down some of the system rails. As a
result, the TLMM hw block may not be operational anymore and wakeup
capable GPIOs will not be detected. The PDC however will be operational
and the GPIOs that are routed to the PDC as IRQs can wake the system up.
To avoid
QCOM SoC's that have Power Domain Controller (PDC) chip in the always-on
domain can wakeup the SoC, when interrupts and GPIOs are routed to its
interrupt controller. Only select GPIOs that are deemed wakeup capable
are routed to specific PDC pins. During low power state, the pinmux
interrupt
GPIOs that are wakeup capable have interrupt lines that are routed to
the always-on interrupt controller (PDC) in parallel to the pinctrl. The
interrupts listed here are the wake up lines corresponding to GPIOs.
Signed-off-by: Lina Iyer
Reviewed-by: Rob Herring
---
Changes in v2:
-
Update the documentation to use interrupts-extended format for
specifying the TLMM summary IRQ line that is requested from GIC and the
PDC interrupts corresponding to the wakeup capable GPIOs.
Update the example to show PDC interrupts for the wakeup capable GPIOs
for SDM845.
Cc:
Enable TLMM IRQs to be sensed by PDC when we enter suspend. It is
possible that the TLMM may be powered off and not detect GPIOs that are
configured as wake up interrupts. By hooking into suspend callbacks, we
allow PDC IRQs to take over and wake up the system if wakeup interrupts
are triggered.
Hi,
Changes in v3:
- Release memory allocated for IRQ anme
- Minor fixes as suggested by Mathias, Bjorn, Evan
Changes in v2:
- Compile and test on 4.18 on SDM845
- Fix IRQ map in patch #3
- Address review comments
(I still need to find a way to
Hi Rob,
Rob Herring wrote on Mon, 27 Aug 2018 20:52:34 -0500:
> In preparation to remove the node name pointer from struct device_node,
> convert printf users to use the %pOFn format specifier.
>
> Cc: Boris Brezillon
> Cc: Miquel Raynal
> Cc: Richard Weinberger
> Cc: David Woodhouse
> Cc:
Hi Gustavo,
"Gustavo A. R. Silva" wrote on Thu, 23 Aug
2018 20:09:38 -0500:
> One of the more common cases of allocation size calculations is finding
> the size of a structure that has a zero-sized array at the end, along
> with memory for some number of elements for that array. For example:
>
Hi Gustavo,
"Gustavo A. R. Silva" wrote on Thu, 23 Aug
2018 14:33:32 -0500:
> One of the more common cases of allocation size calculations is finding
> the size of a structure that has a zero-sized array at the end, along
> with memory for some number of elements for that array. For example:
>
The 'm' kcore_list item could point to kclist_head, and it is incorrect to
look at m->addr / m->size in this case.
There is no choice but to run through the list of entries for every address
if we did not find any entry in the previous iteration
Reset 'm' to NULL in that case at Omar Sandoval's
On 09/03/2018 09:55 AM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 4.18.6 release.
There are 123 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.
Responses should be
Am Dienstag, 4. September 2018, 04:11:07 CEST schrieb Haibo Xu (Arm Technology
China):
> Hi Richard,
>
> What do you mean by done it in the core? moving macro definition to
> include/uapi/linux/ptrace.h?
> The patch is strictly follow x86's sematic on PTRACE_SYSEMU/SINGLESTEP
> support.
Well,
101 - 200 of 1168 matches
Mail list logo
