On Wed, Aug 07, 2019 at 12:31:39AM +0200, Pavel Machek wrote:
Hi!
I'm hoping that whatever problems exynos was having in the past are
somehow magically fixed now and we can make the behavior the same for
all commands.
Dunno. Maybe they are in mainline, but are they fixed in all the
stable rel
> > Does this device support stacked VLAN?
> I am not familiar with stacked VLAN.
> Our HW for sure there is no support. can the SW stack handle it for me?
> Does it mean that the packets can be larger?
If the device does not support it, I believe it's fine to leave it to S/W.
> > Is this really
Hello,
Arnd Bergmann wrote:
> The generic vdso support adds the same #if hack in two places,
> asm/vdso/vdso.h and config-n32-o32-env.c, but only the second
> is actually used. The result lacks the BUILD_VDSO32_64 macro,
> and that triggers a build error:
>
> ./include/linux/page-flags-layout.h:9
Hello,
Zhou Yanjie wrote:
> 1.fix bugs when detecting L2 cache sets value.
> 2.fix bugs when detecting L2 cache ways value.
Series applied to mips-next.
Thanks,
Paul
[ This message was auto-generated; if you believe anything is incorrect
then please email paul.bur...@mips.com to report it
On Wed, 31 Jul 2019, Atish Patra wrote:
> Currently, kernel prints a info warning if any of the extensions
> from "mafdcsu" is missing in device tree. This is not entirely
> correct as Linux can boot with "f or d" extensions if kernel is
> configured accordingly. Moreover, it will continue to prin
A compiler throws a warning on an arm64 system since the
commit 9849a5697d3d ("arch, mm: convert all architectures to use
5level-fixup.h"),
mm/kasan/init.c: In function 'kasan_free_p4d':
mm/kasan/init.c:344:9: warning: variable 'p4d' set but not used
[-Wunused-but-set-variable]
p4d_t *p4d;
Hi all,
Commit
aa733660dbd8 ("openvswitch: Print error when ovs_execute_actions() fails")
is missing a Signed-off-by from its author.
--
Cheers,
Stephen Rothwell
pgpfvIM92z2r0.pgp
Description: OpenPGP digital signature
Yeah I should have sent a pull request last week, so there is a lot
more here than usual. Sorry about that:
1) Fix memory leak in ebtables compat code, from Wenwen Wang.
2) Several kTLS bug fixes from Jakub Kicinski (circular close on
disconnect etc.)
3) Force slave speed check on link sta
Hi Stephen,
My apologies, thanks for the email. Please add the signed-off if you can.
Signed-off-by: Yifeng Sun
Thanks,
Yifeng
On Tue, Aug 6, 2019 at 4:30 PM Stephen Rothwell wrote:
>
> Hi all,
>
> Commit
>
> aa733660dbd8 ("openvswitch: Print error when ovs_execute_actions() fails")
>
> is
On Tue, Aug 06 2019, Jinpu Wang wrote:
> On Tue, Aug 6, 2019 at 9:54 AM Jinpu Wang wrote:
>>
>> On Tue, Aug 6, 2019 at 1:46 AM NeilBrown wrote:
>> >
>> > On Mon, Aug 05 2019, Jinpu Wang wrote:
>> >
>> > > Hi Neil,
>> > >
>> > > For the md higher write IO latency problem, I bisected it to these
On Tue, Jul 30, 2019 at 10:35:31AM -0600, Logan Gunthorpe wrote:
> Here's v2 of the patchset. It doesn't sound like there's anything
> terribly controversial here so this version is mostly just some
> cleanup changes for clarity.
>
> Changes in v2:
> * Rebase on v5.3-rc2 (No changes)
> * Re-intr
Fix two checkpath errors of type:
"open brace '{' following enum go on the same line"
Signed-off-by: Jose Carlos Cazarin Filho
---
drivers/staging/rtl8723bs/include/rtw_mlme.h | 6 ++
1 file changed, 2 insertions(+), 4 deletions(-)
diff --git a/drivers/staging/rtl8723bs/include/rtw_mlme.h
Hi all,
After merging the arm64 tree, today's linux-next build (powerpc
ppc64_defconfig) was just spinning in make - it executing some scripts,
but it was hard to catch just what.
Apparently caused by commit
5cf896fb6be3 ("arm64: Add support for relocating the kernel with RELR
relocations")
On Tue, 2019-08-06 at 21:32 +1000, Michael Ellerman wrote:
> Chris Packham writes:
> >
> > On Mon, 2019-08-05 at 14:06 +1200, Chris Packham wrote:
> > >
> > > Hi All,
> > >
> > > I have a custom board that uses the Freescale/NXP T2080 SoC.
> > >
> > > The board boots fine using v4.19.60 but wh
Currently in Azure cloud, for passthrough devices including GPU, the
host sets the device instance ID's bytes 8 - 15 to a value derived from
the host HWID, which is the same on all devices in a VM. So, the device
instance ID's bytes 8 and 9 provided by the host are no longer unique.
This can cause
On Tue, Aug 06, 2019 at 05:20:40PM -0400, Joel Fernandes (Google) wrote:
> Recently a discussion about performance of system involving a high rate
> of kfree_rcu() calls surfaced on the list [1] which led to another
> discussion how to prepare for this situation.
>
> This patch adds basic batching
On Wed, 31 Jul 2019 16:46:01 +0100 Steven Price wrote:
> Make use of the new functionality in walk_page_range to remove the
> arch page walking code and use the generic code to walk the page tables.
>
> The effective permissions are passed down the chain using new fields
> in struct pg_state.
>
On 8/6/19 3:00 PM, Heiner Kallweit wrote:
> On 06.08.2019 23:09, Tao Ren wrote:
>> The BCM54616S PHY cannot work properly in RGMII->1000Base-KX mode (for
>> example, on Facebook CMM BMC platform), mainly because genphy functions
>> are designed for copper links, and 1000Base-X (clause 37) auto nego
On Fri, 2 Aug 2019, Christoph Hellwig wrote:
> On Fri, Jul 26, 2019 at 01:00:49PM -0700, Paul Walmsley wrote:
> >
> > The RISC-V specifications currently define three virtual memory
> > translation systems: Sv32, Sv39, and Sv48. Sv32 is currently specific
> > to 32-bit systems; Sv39 and Sv48 are
On Fri, Aug 02, 2019 at 08:14:49AM -0700, Paul E. McKenney wrote:
> Use of the rcu_data structure's segmented ->cblist for no-CBs CPUs
> takes advantage of unrelated grace periods, thus reducing the memory
> footprint in the face of floods of call_rcu() invocations. However,
> the ->cblist field i
On Tue, 6 Aug 2019 18:00:12 +0800
Leo Yan wrote:
> This small patch set is to add support for function error injection;
> this can be used to eanble more advanced debugging feature, e.g.
> CONFIG_BPF_KPROBE_OVERRIDE.
>
> The patch 01/03 is to consolidate the function definition which can be
> s
Hi all,
After merging the qcom tree, today's linux-next build (x86_64
allmodconfig) produced this warning:
drivers/soc/qcom/socinfo.c: In function 'socinfo_debugfs_init':
drivers/soc/qcom/socinfo.c:323:3: warning: this statement may fall through
[-Wimplicit-fallthrough=]
debugfs_create_x32("r
On Tue, Aug 06, 2019 at 08:03:13PM -0400, Joel Fernandes wrote:
> On Fri, Aug 02, 2019 at 08:14:49AM -0700, Paul E. McKenney wrote:
> > Use of the rcu_data structure's segmented ->cblist for no-CBs CPUs
> > takes advantage of unrelated grace periods, thus reducing the memory
> > footprint in the fa
Currently BMC's MAC address is calculated by adding 1 to NCSI NIC's base
MAC address when CONFIG_NCSI_OEM_CMD_GET_MAC option is enabled. The logic
doesn't work for platforms with different BMC MAC offset: for example,
Facebook Yamp BMC's MAC address is calculated by adding 2 to NIC's base
MAC addre
From: Andrei Vagin
Time Namespace isolates clock values.
The kernel provides access to several clocks CLOCK_REALTIME,
CLOCK_MONOTONIC, CLOCK_BOOTTIME, etc.
CLOCK_REALTIME
System-wide clock that measures real (i.e., wall-clock) time.
CLOCK_MONOTONIC
Clock that cannot be set and repr
Hi all,
Today's linux-next merge of the mips tree got a conflict in:
arch/mips/include/asm/vdso/vdso.h
( arch/mips/vdso/vdso.h in Linus' tree)
between commit:
ee38d94a0ad8 ("page flags: prioritize kasan bits over last-cpuid")
from Linus' tree and commit:
6393e6064486 ("mips: fix vdso32
As it has been discussed on timens RFC, adding a new conditional branch
`if (inside_time_ns)` on VDSO for all processes is undesirable.
It will add a penalty for everybody as branch predictor may mispredict
the jump. Also there are instruction cache lines wasted on cmp/jmp.
Those effects of introd
On Tue, Aug 06, 2019 at 05:20:41PM -0400, Joel Fernandes (Google) wrote:
> This test runs kfree_rcu in a loop to measure performance of the new
> kfree_rcu, with and without patch.
>
> To see improvement, run with boot parameters:
> rcuperf.kfree_loops=2000 rcuperf.kfree_alloc_num=100 rcuperf.perf
The pull request you sent on Tue, 06 Aug 2019 16:35:57 -0700 (PDT):
> git://git.kernel.org/pub/scm/linux/kernel/git/netdev/net.git refs/heads/master
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/33920f1ec5bf47c5c0a1d2113989bdd9dfb3fae9
Thank you!
--
Deet-doot-dot,
On Tue, 2019-08-06 at 13:34 +0100, Mark Rutland wrote:
> On Tue, Aug 06, 2019 at 07:29:48PM +0800, Miles Chen wrote:
> > This change prints the hexadecimal EC value in mem_abort_decode(),
> > which makes it easier to lookup the corresponding EC in
> > the ARM Architecture Reference Manual.
> >
> >
+ yhchuang
On Tue, Aug 6, 2019 at 7:32 AM 고준 wrote:
>
> Hello,
>
> I recently reported a bug to Ubuntu regarding a regression in wireless
> driver support for the Realtek r8822be wireless chipset. The issue
> link on launchpad is:
>
> https://bugs.launchpad.net/bugs/1838133
>
> After Canonical de
On Tue, Aug 06, 2019 at 11:29:52AM +0200, Vlastimil Babka wrote:
>On 8/6/19 10:11 AM, Wei Yang wrote:
>> When addr is out of the range of the whole rb_tree, pprev will points to
>> the biggest node. find_vma_prev gets is by going through the right most
>
>s/biggest/last/ ? or right-most?
>
>> node
On 2019-08-06 5:44 p.m., Bjorn Helgaas wrote:
> On Tue, Jul 30, 2019 at 10:35:31AM -0600, Logan Gunthorpe wrote:
>> Here's v2 of the patchset. It doesn't sound like there's anything
>> terribly controversial here so this version is mostly just some
>> cleanup changes for clarity.
>>
>> Changes i
clang errors:
drivers/pinctrl/aspeed/pinctrl-aspeed-g6.c:2325:9: error: incompatible
pointer types initializing 'int (*)(struct aspeed_pinmux_data *, const
struct aspeed_sig_expr *, bool)' with an expression of type 'int (const
struct aspeed_pinmux_data *, const struct aspeed_sig_expr *, bool)'
[-
On Tue, Aug 06, 2019 at 10:58:22AM +, Balbir Singh wrote:
>On Tue, Aug 06, 2019 at 04:11:23PM +0800, Wei Yang wrote:
>> When addr is out of the range of the whole rb_tree, pprev will points to
>> the biggest node. find_vma_prev gets is by going through the right most
>> node of the tree.
>>
>>
This change prints the hexadecimal EC value in mem_abort_decode(),
which makes it easier to lookup the corresponding EC in
the ARM Architecture Reference Manual.
The commit 1f9b8936f36f ("arm64: Decode information from ESR upon mem
faults") prints useful information when memory abort occurs. It wo
On Tue, Aug 06, 2019 at 08:03:13PM -0400, Joel Fernandes wrote:
> On Fri, Aug 02, 2019 at 08:14:49AM -0700, Paul E. McKenney wrote:
> > Use of the rcu_data structure's segmented ->cblist for no-CBs CPUs
> > takes advantage of unrelated grace periods, thus reducing the memory
> > footprint in the fa
On Wed, 7 Aug 2019, at 10:02, Nathan Chancellor wrote:
> clang errors:
>
> drivers/pinctrl/aspeed/pinctrl-aspeed-g6.c:2325:9: error: incompatible
> pointer types initializing 'int (*)(struct aspeed_pinmux_data *, const
> struct aspeed_sig_expr *, bool)' with an expression of type 'int (const
>
The ASPEED SD/SDIO/MMC controller exposes two slots implementing the
SDIO Host Specification v2.00, with 1 or 4 bit data buses, or an 8 bit
data bus if only a single slot is enabled.
Signed-off-by: Andrew Jeffery
---
v4:
* Make use of mmc-controller.yaml
* Document sdhci,auto-cmd12
v2:
* Fix co
Hello,
v5 of the ASPEED SDHCI patches fixes an error-path cleanup issue pointed out by
Adrian.
v4 can be found here:
http://patchwork.ozlabs.org/cover/1141949/
Please review!
Andrew
Andrew Jeffery (2):
dt-bindings: mmc: Document Aspeed SD controller
mmc: Add support for the ASPEED SD cont
Add a minimal driver for ASPEED's SD controller, which exposes two
SDHCIs.
The ASPEED design implements a common register set for the SDHCIs, and
moves some of the standard configuration elements out to this common
area (e.g. 8-bit mode, and card detect configuration which is not
currently support
On Tue, 6 Aug 2019 17:35:01 -0700
"Paul E. McKenney" wrote:
> > > + // Don't use ->nocb_bypass during early boot.
> >
> > Very minor nit: comment style should be /* */
>
> I thought that Linus said that "//" was now OK. Am I confused?
Have a link?
-- Steve
: CPU: 25 PID: 1 at drivers/base/core.c:691
device_links_supplier_sync_state_resume+0x100/0x128
[ 95.006062][T1] Modules linked in:
[ 95.009815][T1] CPU: 25 PID: 1 Comm: swapper/0 Not tainted
5.3.0-rc3-next-20190806+ #11
[ 95.018161][T1] Hardware name: HPE Apollo 70
On 2019/8/6 16:36, Vlastimil Babka wrote:
> On 8/6/19 4:36 AM, Kefeng Wang wrote:
[...]
>>
>> [QUESTION]
>>
>> SYSCALL_DEFINE4(migrate_pages, pid_t, pid, unsigned long, maxnode,
>> const unsigned long __user *, old_nodes,
>> const unsigned long __user *, new_nodes
On Tue, Aug 06, 2019 at 02:15:03PM +0300, Daniel Baluta wrote:
> On Tue, Jul 30, 2019 at 10:59 AM Nicolin Chen wrote:
> >
> > On Mon, Jul 29, 2019 at 09:20:01PM +0100, Mark Brown wrote:
> > > On Mon, Jul 29, 2019 at 10:57:43PM +0300, Daniel Baluta wrote:
> > > > On Mon, Jul 29, 2019 at 10:42 PM Ni
The mm-of-the-moment snapshot 2019-08-06-18-11 has been uploaded to
http://www.ozlabs.org/~akpm/mmotm/
mmotm-readme.txt says
README for mm-of-the-moment:
http://www.ozlabs.org/~akpm/mmotm/
This is a snapshot of my -mm patch queue. Uploaded at random hopefully
more than once a week.
You wi
On Tue, 2019-08-06 at 16:27 -0700, Paul Walmsley wrote:
> On Wed, 31 Jul 2019, Atish Patra wrote:
>
> > Currently, kernel prints a info warning if any of the extensions
> > from "mafdcsu" is missing in device tree. This is not entirely
> > correct as Linux can boot with "f or d" extensions if kern
Chris Packham writes:
> On Tue, 2019-08-06 at 21:32 +1000, Michael Ellerman wrote:
>> Chris Packham writes:
>> > On Mon, 2019-08-05 at 14:06 +1200, Chris Packham wrote:
>> > >
>> > > Hi All,
>> > >
>> > > I have a custom board that uses the Freescale/NXP T2080 SoC.
>> > >
>> > > The board boot
On Tue, Aug 06, 2019 at 06:23:27PM +0300, Daniel Baluta wrote:
> On Mon, Jul 29, 2019 at 11:22 PM Nicolin Chen wrote:
> >
> > On Sun, Jul 28, 2019 at 10:24:25PM +0300, Daniel Baluta wrote:
> > > SAI supports up to 8 Rx/Tx data lines which can be enabled
> > > using TCE/RCE bits of TCR3/RCR3 regist
On Tue, Aug 06, 2019 at 06:12:10PM +0300, Daniel Baluta wrote:
> SAI IP supports up to 8 data lines. The configuration of
> supported number of data lines is decided at SoC integration
> time.
>
> This patch adds definitions for all related data TX/RX registers:
> * TDR0..7, Transmit data re
On Tue, Aug 06, 2019 at 06:12:11PM +0300, Daniel Baluta wrote:
> Tx channel enable (TCE) / Rx channel enable (RCE) bits
> enable corresponding data channel for Tx/Rx operation.
>
> Because SAI supports up the 8 channels TCE/RCE occupy
> up the 8 bits inside TCR3/RCR3 registers we need to extend
>
On Tue, Aug 06, 2019 at 08:40:55PM -0400, Steven Rostedt wrote:
> On Tue, 6 Aug 2019 17:35:01 -0700
> "Paul E. McKenney" wrote:
>
> > > > + // Don't use ->nocb_bypass during early boot.
> > >
> > > Very minor nit: comment style should be /* */
> >
> > I thought that Linus said that "/
On Mon, Aug 5, 2019 at 11:48 PM Andy Shevchenko
wrote:
>
> On Mon, Aug 5, 2019 at 10:36 PM Andrey Smirnov
> wrote:
> >
> > The vast majority of the serial drivers check for
> >
> > uart_tx_stopped(&p->port) || uart_circ_empty(xmit)
> >
> > condition one or more times. Create a dedicated help
0/0x128
> [ 95.006062][T1] Modules linked in:
> [ 95.009815][T1] CPU: 25 PID: 1 Comm: swapper/0 Not tainted
> 5.3.0-rc3-next-20190806+ #11
> [ 95.018161][T1] Hardware name: HPE Apollo 70
> /C01_APACHE_MB , BIOS L50_5
On Tue, 6 Aug 2019 18:17:07 -0700
"Paul E. McKenney" wrote:
> On Tue, Aug 06, 2019 at 08:40:55PM -0400, Steven Rostedt wrote:
> > On Tue, 6 Aug 2019 17:35:01 -0700
> > "Paul E. McKenney" wrote:
> >
> > > > > + // Don't use ->nocb_bypass during early boot.
> > > >
> > > > Very minor n
On Wed, 2019-08-07 at 11:13 +1000, Michael Ellerman wrote:
> Chris Packham writes:
> >
> > On Tue, 2019-08-06 at 21:32 +1000, Michael Ellerman wrote:
> > >
> > > Chris Packham writes:
> > > >
> > > > On Mon, 2019-08-05 at 14:06 +1200, Chris Packham wrote:
> > > > >
> > > > >
> > > > > Hi All
Introduce fall through annotations in the switch statements of
socinfo_debugfs_init() to silence compiler warnings.
Fixes: 9c84c1e78634 ("soc: qcom: socinfo: Expose custom attributes")
Reported-by: Stephen Rothwell
Signed-off-by: Bjorn Andersson
---
drivers/soc/qcom/socinfo.c | 11 +++
On Wed, 7 Aug 2019, Atish Patra wrote:
> On Tue, 2019-08-06 at 16:27 -0700, Paul Walmsley wrote:
>
> > Seems like the "su" should be dropped from mandatory_ext. What do you
> > think?
> >
>
> Yup. As DT binding only mention imafdc, mandatory extensions should
> contain only that and just cons
On Wed, Aug 07, 2019 at 09:08:11AM +0900, Masami Hiramatsu wrote:
> On Tue, 6 Aug 2019 18:00:12 +0800
> Leo Yan wrote:
>
> > This small patch set is to add support for function error injection;
> > this can be used to eanble more advanced debugging feature, e.g.
> > CONFIG_BPF_KPROBE_OVERRIDE.
>
Hello Christoph,
Thanks for your review.
Christoph Hellwig writes:
> On Tue, Aug 06, 2019 at 02:22:34AM -0300, Thiago Jung Bauermann wrote:
>> @@ -1318,7 +1319,10 @@ void iommu_init_early_pSeries(void)
>> of_reconfig_notifier_register(&iommu_reconfig_nb);
>> register_memory_notifier
From: John Hubbard
For pages that were retained via get_user_pages*(), release those pages
via the new put_user_page*() routines, instead of via put_page() or
release_pages().
This is part a tree-wide conversion, as described in commit fc1d8e7cca2d
("mm: introduce put_user_page*(), placeholder v
On Wed, Aug 7, 2019 at 1:13 AM James Smart wrote:
>
> On 8/5/2019 6:09 PM, Ming Lei wrote:
> >
> > I am wondering why you use 2 * num_possible_nodes() as the limit instead of
> > num_possible_nodes(), could you explain it a bit?
>
> The number comes from most systems being dual socket systems, thu
On Tue, Aug 06, 2019 at 06:12:12PM +0300, Daniel Baluta wrote:
> New IP version introduces Version ID and Parameter registers
> and optionally added Timestamp feature.
>
> VERID and PARAM registers are placed at the top of registers
> address space and some registers are shifted according to
> the
From: John Hubbard
For pages that were retained via get_user_pages*(), release those pages
via the new put_user_page*() routines, instead of via put_page() or
release_pages().
This is part a tree-wide conversion, as described in commit fc1d8e7cca2d
("mm: introduce put_user_page*(), placeholder v
Hi,
On 8/6/19 8:24 PM, Bjorn Andersson wrote:
> Introduce fall through annotations in the switch statements of
> socinfo_debugfs_init() to silence compiler warnings.
>
This is enough to silence all the warnings:
diff --git a/drivers/soc/qcom/socinfo.c b/drivers/soc/qcom/socinfo.c
index 855353be
From: John Hubbard
For pages that were retained via get_user_pages*(), release those pages
via the new put_user_page*() routines, instead of via put_page() or
release_pages().
This is part a tree-wide conversion, as described in commit fc1d8e7cca2d
("mm: introduce put_user_page*(), placeholder v
On Tue, Aug 06, 2019 at 06:12:14PM +0300, Daniel Baluta wrote:
> For i.MX7ULP and i.MX8MQ register map is changed. Add two new compatbile
> strings to differentiate this.
>
> Signed-off-by: Daniel Baluta
Looks good to me. As long as one of DT maintainers acks,
Acked-by: Nicolin Chen
Thanks
>
Define watchdog_allowed_mask only when SOFTLOCKUP_DETECTOR is enabled.
Signed-off-by: Santosh Sivaraj
---
kernel/watchdog.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/kernel/watchdog.c b/kernel/watchdog.c
index 7f9e7b9306fe..d365616f9ed3 100644
--- a/kernel/watchdog.c
On 2019/8/6 21:41, Jay Vosburgh wrote:
> YueHaibing wrote:
>
>> As commit 30d8177e8ac7 ("bonding: Always enable vlan tx offload")
>> said, we should always enable bonding's vlan tx offload, pass the
>> vlan packets to the slave devices with vlan tci, let them to handle
>> vlan implementation.
>>
-
>> [ 94.989827][T1] Unmatched sync_state pause/resume!
>> [ 94.989894][T1] WARNING: CPU: 25 PID: 1 at drivers/base/core.c:691
>> device_links_supplier_sync_state_resume+0x100/0x128
>> [ 95.006062][T1] Modules linked in:
>> [ 95.009815][T1]
wakeup_source_init() has no users. Remove it.
As a result, wakeup_source_prepare() is only called from
wakeup_source_create(). Merge wakeup_source_prepare() into
wakeup_source_create() and remove it.
Change wakeup_source_create() behavior so that assigning NULL to wakeup
source's name throws an e
Add an ID and a device pointer to 'struct wakeup_source'. Use them to to
expose wakeup sources statistics in sysfs under
/sys/class/wakeup/wakeup/*.
Co-developed-by: Greg Kroah-Hartman
Signed-off-by: Greg Kroah-Hartman
Co-developed-by: Stephen Boyd
Signed-off-by: Stephen Boyd
Signed-off-by: Tr
kernel/power/wakelock.c duplicates wakeup source creation and
registration code from drivers/base/power/wakeup.c.
Change struct wakelock's wakeup source to a pointer and use
wakeup_source_register() function to create and register said wakeup
source. Use wakeup_source_unregister() on cleanup path.
Userspace can use wakeup_sources debugfs node to plot history of suspend
blocking wakeup sources over device's boot cycle. This information can
then be used (1) for power-specific bug reporting and (2) towards
attributing battery consumption to specific processes over a period of
time.
However, de
started
> >> [ 94.812338][ T1368] pcieport :0f:00.0: Adding to iommu group 0
> >> [ 94.984466][T1] [ cut here ]
> >> [ 94.989827][ T1] Unmatched sync_state pause/resume!
> >> [ 94.989894][T1] WARNING: CPU: 25 PID: 1 at drivers/base/core.c:691
> >>
From: Srinivas Kandagatla Sent: Tuesday,
August 6, 2019 6:04 PM
> On 04/07/2019 15:20, fugang.d...@nxp.com wrote:
> > From: Fugang Duan
> >
> > i.MX8QM efuse table has some difference with i.MX8QXP platform, so add
> > i.MX8QM platform support.
> >
> > Signed-off-by: Fugang Duan
> > ---
> > d
Hi Bjorn,
On Tue, 6 Aug 2019 18:24:57 -0700 Bjorn Andersson
wrote:
>
> qcom_socinfo->dbg_root,
> &qcom_socinfo->info.raw_device_num);
> + /* Fall through */
> case SOCINFO_VERSION(0, 11):
> + /* Fall
On Tue, 2019-08-06 at 17:33 -0400, Sasha Levin wrote:
> From: Paul Wise
>
> [ Upstream commit 315c69261dd3fa12dbc830d4fa00d1fad98d3b03 ]
The patch changes the behaviour of the interface between the Linux
kernel and userspace core dump handlers. The previous behaviour was
unlikely to be depended
Hi Yifeng,
On Tue, 6 Aug 2019 16:37:26 -0700 Yifeng Sun wrote:
>
> My apologies, thanks for the email. Please add the signed-off if you can.
Dave does not rebase his trees, so that is not possible. Just remember
for next time, thanks :-)
--
Cheers,
Stephen Rothwell
pgpsJqsY4ng0g.pgp
Descrip
tarted
>>>> [ 94.812338][ T1368] pcieport :0f:00.0: Adding to iommu group 0
>>>> [ 94.984466][T1] [ cut here ]
>>>> [ 94.989827][T1] Unmatched sync_state pause/resume!
>>>> [ 94.989894][T1] WARNING:
Sorry folks, I haven't properly tested this before sending the patch
After I've removed the cast, I got this error:
drivers/staging/rtl8712/rtl871x_ioctl_linux.c:668:13: error: SSE
register return with SSE disabled
(fwrq->m >= 2.412e8) &&
~^~~
But I think it's strange sinc
Hi Stephen,
Sure, thanks!
Yifeng
On Tue, Aug 6, 2019 at 6:54 PM Stephen Rothwell wrote:
>
> Hi Yifeng,
>
> On Tue, 6 Aug 2019 16:37:26 -0700 Yifeng Sun wrote:
> >
> > My apologies, thanks for the email. Please add the signed-off if you can.
>
> Dave does not rebase his trees, so that is not pos
Dear Friend,
I need you to please let me know if there are fast growing investments
in your country in which i can invest money in. I have access to a
huge amount of money, which i want to invest in your country, i want
to know if you can be an agent/partner to me and i will give you a
commission
In platforms/devices which have CONFIG_OF turned on but don't have a
populated DT, the calls to device_links_supplier_sync_state_pause() and
device_links_supplier_sync_state_resume() can get mismatched. This will
cause a warning during boot. Fix the warning by making sure the calls are
matched even
In preparation for removing __udivdi3() from the RISC-V
architecture-specific files, convert its one user to use do_div().
This avoids breaking the RV32 build after __udivdi3() is removed.
Signed-off-by: Paul Walmsley
---
arch/riscv/lib/delay.c | 7 ++-
1 file changed, 6 insertions(+), 1 d
Currently THP deferred split shrinker is not memcg aware, this may cause
premature OOM with some configuration. For example the below test would
run into premature OOM easily:
$ cgcreate -g memory:thp
$ echo 4G > /sys/fs/cgroup/memory/thp/memory/limit_in_bytes
$ cgexec -g memory:thp transhuge-st
Put split_queue, split_queue_lock and split_queue_len into a struct in
order to reduce code duplication when we convert deferred_split to memcg
aware in the later patches.
Suggested-by: "Kirill A . Shutemov"
Cc: Kirill Tkhai
Cc: Johannes Weiner
Cc: Michal Hocko
Cc: Hugh Dickins
Cc: Shakeel Bu
Currently THP deferred split shrinker is not memcg aware, this may cause
premature OOM with some configuration. For example the below test would
run into premature OOM easily:
$ cgcreate -g memory:thp
$ echo 4G > /sys/fs/cgroup/memory/thp/memory/limit_in_bytes
$ cgexec -g memory:thp transhuge-stre
The later patch would make THP deferred split shrinker memcg aware, but
it needs page->mem_cgroup information in THP destructor, which is called
after mem_cgroup_uncharge() now.
So, move mem_cgroup_uncharge() from __page_cache_release() to compound
page destructor, which is called by both THP and
On Tue 06 Aug 18:50 PDT 2019, Stephen Rothwell wrote:
> Hi Bjorn,
>
> On Tue, 6 Aug 2019 18:24:57 -0700 Bjorn Andersson
> wrote:
> >
> >qcom_socinfo->dbg_root,
> >&qcom_socinfo->info.raw_device_num);
> > + /* Fall throug
Currently shrinker is just allocated and can work when memcg kmem is
enabled. But, THP deferred split shrinker is not slab shrinker, it
doesn't make too much sense to have such shrinker depend on memcg kmem.
It should be able to reclaim THP even though memcg kmem is disabled.
Introduce a new shri
As commit 30d8177e8ac7 ("bonding: Always enable vlan tx offload")
said, we should always enable bonding's vlan tx offload, pass the
vlan packets to the slave devices with vlan tci, let them to handle
vlan implementation.
Now if encapsulation protocols like VXLAN is used, skb->encapsulation
may be
From: Song Hui
Update the NXP GPIO node dt-binding file for QorIQ and
Layerscape platforms, and add one more example with
ls1028a GPIO node.
Signed-off-by: Song Hui
---
Documentation/devicetree/bindings/gpio/gpio-mpc8xxx.txt | 16 +++-
1 file changed, 15 insertions(+), 1 deletion(-
Introduce fall through annotations in the switch statements of
socinfo_debugfs_init() to silence compiler warnings.
Fixes: 9c84c1e78634 ("soc: qcom: socinfo: Expose custom attributes")
Reported-by: Stephen Rothwell
Signed-off-by: Bjorn Andersson
---
drivers/soc/qcom/socinfo.c | 8
1 fi
On Mon, Aug 05, 2019 at 04:41:12PM +0200, Pavel Machek wrote:
Hi!
[ Upstream commit 1c0479023412ab7834f2e98b796eb0d8c627cd62 ]
As some point hs200 was failing on rk3288-veyron-minnie. See commit
984926781122 ("ARM: dts: rockchip: temporarily remove emmc hs200 speed
from rk3288 minnie"). Alth
The baseline ISA support requirement for the RISC-V Linux kernel
mandates compressed instructions, so it doesn't make sense for
compressed instruction support to be configurable.
Signed-off-by: Paul Walmsley
Cc: Atish Patra
---
arch/riscv/Kconfig | 10 --
arch/riscv/Makefile | 2 +-
Hi.
On Tue, Aug 6, 2019 at 7:56 PM Vasily Gorbik wrote:
>
> Define and export OBJSIZE variable for "size" tool from binutils to be
> used in architecture specific Makefiles (naming the variable just "SIZE"
> would be too risky). In particular this tool is useful to perform checks
> that early boo
> + yhchuang
>
> On Tue, Aug 6, 2019 at 7:32 AM 고준 wrote:
> >
> > Hello,
> >
> > I recently reported a bug to Ubuntu regarding a regression in wireless
> > driver support for the Realtek r8822be wireless chipset. The issue
> > link on launchpad is:
> >
> > https://bugs.launchpad.net/bugs/1838133
On Tue, Aug 6, 2019 at 7:56 PM Vasily Gorbik wrote:
>
> Currently empty .bss checks performed do not pay attention to "common
> objects" in object files which end up in .bss section eventually.
>
> The "size" tool is a part of binutils and since version 2.18 provides
> "--common" command line opti
On Tue, Aug 6, 2019 at 4:50 PM Stephen Rothwell wrote:
>
> Hi all,
>
> After merging the arm64 tree, today's linux-next build (powerpc
> ppc64_defconfig) was just spinning in make - it executing some scripts,
> but it was hard to catch just what.
>
> Apparently caused by commit
>
> 5cf896fb6be3
801 - 900 of 1002 matches
Mail list logo