Pure ocd, but this one has been bugging me for a while.
Signed-off-by: Rui Salvaterra
---
net/netfilter/nf_conntrack_helper.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/net/netfilter/nf_conntrack_helper.c
b/net/netfilter/nf_conntrack_helper.c
index
On Wed, 24 Jul 2019, Steven Price wrote:
> On 24/07/2019 14:57, Thomas Gleixner wrote:
> > From your 14/N changelog:
> >
> >> This keeps the output shorter and will help with a future change
> >
> > I don't care about shorter at all. It's debug information.
>
> Sorry, the "shorter" part was
On Wed, 2019-07-24 at 14:17 +, Moore, Robert wrote:
>
> -Original Message-
> From: Qian Cai [mailto:c...@lca.pw]
> Sent: Wednesday, July 24, 2019 6:40 AM
> To: Moore, Robert ; Nick Desaulniers gle.com>
> Cc: Wysocki, Rafael J ; Schmauss, Erik u...@intel.com>; j...@freebsd.org; Len
Second patch just registers the PCIe endpoint device containing
the MDIO registers as a standalone MDIO bus driver, to allow
an alternative way to control the MDIO bus. The same code used
by the ENETC ports (eth controllers) to manage MDIO via local
registers applies and is reused.
Bindings are
LS1028a has one Ethernet management interface. On the QDS board, the
MDIO signals are multiplexed to either on-board AR8035 PHY device or
to 4 PCIe slots allowing for SGMII cards.
To enable the Ethernet ENETC Port 1, which can only be connected to a
RGMII PHY, the multiplexer needs to be
The on-chip PCIe root complex that integrates the ENETC ethernet
controllers also integrates a PCIe enpoint for the MDIO controller
provinding for cetralized control of the ENETC mdio bus.
Add bindings for this "central" MDIO Integrated PCIe Endpoit.
Signed-off-by: Claudiu Manoil
---
v1 - none
Though it works, this is not how it should have been.
What's needed is a pointer to the mdio registers.
Store it properly inside bus->priv allocated space.
Use devm_* variant to further clean up the init error /
remove paths.
Fixes following sparse warning:
warning: incorrect type in assignment
Hi there
I have a laptop AMD A12 with amdgpu.
When I use kernel 5.X I have trouble with powerplay!
https://paste.ubuntu.com/p/YhbjnzYYYh/
Is there same kernel boot parameters to use in order to disable powerplay??
Thanks
ENETC ports can manage the MDIO bus via local register
interface. However there's also a centralized way
to manage the MDIO bus, via the MDIO PCIe endpoint
device integrated by the same root complex that also
integrates the ENETC ports (eth controllers).
Depending on board design and use case,
On Sun, Jul 21, 2019 at 7:51 PM Shawn Guo wrote:
>
> On Wed, Jun 19, 2019 at 01:52:43PM +0800, anson.hu...@nxp.com wrote:
> > From: Anson Huang
> >
> > Add the clock binding doc for i.MX8MN.
> >
> > Signed-off-by: Anson Huang
> > Reviewed-by: Maxime Ripard
>
> Applied all, thanks.
This breaks
On 7/24/19 7:15 AM, Masanari Iida wrote:
> This patch fixes some spelling typo in qos_mc_aware.sh
>
> Signed-off-by: Masanari Iida
Acked-by: Randy Dunlap
Thanks.
> ---
> tools/testing/selftests/drivers/net/mlxsw/qos_mc_aware.sh | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
Hey everyone,
This adds the ability to wait on processes using pidfds. This is one of
the few missing pieces to make it possible to manage processes using
only pidfds.
pidfd_wait() does explicitly not allow scoping of the process referred
to by the pidfd, i.e. generic wait requests such as
The code here uses a struct waitid_info to catch basic information about
process exit including the pid, uid, status, and signal that caused the
process to exit. This information is then stuffed into a struct siginfo
for the waitid() syscall. That seems like an odd thing to do. We can
just pass
This adds the pidfd_wait() syscall.
One of the last remaining bits for the pidfd api is to make it possible
to wait on pidfds. With this syscall implemented parts of userspace that
want to use this api can finally switch to managing processes completely
through pidfds if they so desire (cf. [1]).
If CLONE_WAIT_PID is set the newly created process will not be
considered by process wait requests that wait generically on children
such as:
syscall(__NR_wait4, -1, wstatus, options, rusage)
syscall(__NR_waitpid, -1, wstatus, options)
syscall(__NR_waitid, P_ALL, -1,
Add tests for pidfd_wait() and CLONE_WAIT_PID:
- test that pidfd_wait() syscall is supported
- test that pidfd_wait() does not accept unknown flags
- test that pidfd_wait() can wait on a pidfd
- test that pidfd_wait() can wait on a pidfd and return struct rusage
- test that pidfd_wait() can wait
On Tue, Jul 23 2019 at 14:11 -0600, Stephen Boyd wrote:
Quoting Lina Iyer (2019-07-22 14:53:38)
Avoid locking in the interrupt context to improve latency. Since we
don't lock in the interrupt context, it is possible that we now could
race with the DRV_CONTROL register that writes the enable
On Fri, 5 Jul 2019 11:57:12 +0200, Niklas Cassel wrote:
> From: Sricharan R
>
> The kryo cpufreq driver reads the nvmem cell and uses that data to
> populate the opps. There are other qcom cpufreq socs like krait which
> does similar thing. Except for the interpretation of the read data,
> rest
On Tue, Jul 23 2019 at 14:19 -0600, Stephen Boyd wrote:
Quoting Lina Iyer (2019-07-23 12:21:59)
On Tue, Jul 23 2019 at 12:22 -0600, Stephen Boyd wrote:
>Quoting Lina Iyer (2019-07-22 14:53:37)
>> From: "Raju P.L.S.S.S.N"
>>
>> The tcs->lock was introduced to serialize access with in TCS group.
On Wed, Jul 24, 2019 at 09:20:56AM +0200, Greg KH wrote:
> On Tue, Jul 23, 2019 at 10:20:12PM -0700, Moritz Fischer wrote:
> > The following changes since commit 5f9e832c137075045d15cd6899ab0505cfb2ca4b:
> >
> > Linus 5.3-rc1 (2019-07-21 14:05:38 -0700)
> >
> > are available in the Git
Commit-ID: 4599c6671b8119ed5455e4ed6b967b461c27a9f7
Gitweb: https://git.kernel.org/tip/4599c6671b8119ed5455e4ed6b967b461c27a9f7
Author: Nikolas Nyby
AuthorDate: Wed, 24 Jul 2019 00:13:37 -0400
Committer: Thomas Gleixner
CommitDate: Wed, 24 Jul 2019 16:50:15 +0200
x86/crash: Remove
On Fri, 5 Jul 2019 11:57:14 +0200, Niklas Cassel wrote:
> Not all Qualcomm platforms need to care about the speedbin efuse,
> nor the value blown into the speedbin efuse.
> Therefore, make the nvmem-cells and opp-supported-hw properties
> optional.
>
> Signed-off-by: Niklas Cassel
> ---
>
On Tue, Jul 23, 2019 at 09:40:51AM -0500, Thor Thayer wrote:
> Hi Moritz,
>
> On 7/21/19 7:59 PM, Moritz Fischer wrote:
> > Thor,
> >
> > On Tue, Jul 16, 2019 at 05:48:06PM -0500, thor.tha...@linux.intel.com wrote:
> > > From: Thor Thayer
> > >
> > > In preparation for adding newer V2 parts
On Wed, Jul 24, 2019 at 11:15:54PM +0900, Masanari Iida wrote:
> This patch fixes some spelling typo in qos_mc_aware.sh
>
> Signed-off-by: Masanari Iida
Thanks for the patch, but it should go through the networking tree.
Please resubmit to net...@vger.kernel.org and make sure subject prefix
is
> Let's consolidate all these error messages into the API itself,
> allowing us to get rid of the error messages in each driver.
Such information from the commit descriptions sounds positive.
> +++ b/drivers/base/platform.c
…
> @@ -163,6 +158,22 @@ int platform_get_irq(struct platform_device
Some arches (e.g., arm64, x86) have moved towards non-executable
module_alloc() allocations for security hardening reasons. That means
that the module loader will need to set the text section of a module to
executable, regardless of whether or not CONFIG_STRICT_MODULE_RWX is set.
When
Pavel
On 7/24/19 7:45 AM, Pavel Machek wrote:
Hi!
So now the backlight LED can be controlled. Good. (And thanks!)
But I seem to remember that backlight had range from "is it really on?"
to "very bright"; now it seems to have range from "bright" to "very
bright".
Any ideas what goes on
On Wed, Jul 24, 2019 at 05:41:38PM +0300, Claudiu Manoil wrote:
> Though it works, this is not how it should have been.
> What's needed is a pointer to the mdio registers.
> Store it properly inside bus->priv allocated space.
> Use devm_* variant to further clean up the init error /
> remove
Add an extra condition to add the video output control class when the
device has some hdmi outputs defined. This is required to then always
be able to add the display present control, which is enabled when
there are some hdmi outputs.
This fixes the corner case where no_error_inj is enabled and
Hi Masami,
I wanted to revisit FTRACE_OPS_FL_IPMODIFY blocking of kprobes and
livepatch, at least in cases where kprobe pre_handlers don't modify
regs->ip.
(We've discussed this previously at part of a kpatch github issue #47:
https://github.com/dynup/kpatch/issues/47)
The particular use case I
From: Thor Thayer
The current Cadence QSPI driver sometimes caused a
"rcu_sched self-detected stall" while writing large files.
Stall Report:
'# mtd_debug write /dev/mtd1 0 48816464 blob.img
[ 1815.454227] rcu: INFO: rcu_sched self-detected stall on CPU
[ 1815.459789] rcu: 0-: (2099
Pavel
On 7/24/19 7:45 AM, Pavel Machek wrote:
+
static int lm3532_parse_node(struct lm3532_data *priv)
{
struct fwnode_handle *child = NULL;
@@ -536,11 +579,13 @@ static int lm3532_parse_node(struct lm3532_data *priv)
ret = fwnode_property_read_u32(child,
Simplify the timerqueue code by using cached rbtrees and rely on the tree
leftmost node semantics to get the timer with earliest expiration time.
This is a drop in conversion, and therefore semantics remain untouched.
The runtime overhead of cached rbtrees is be pretty much the same as the
In order to support IPI/NMI broadcasting via the shorthand mechanism side
effects of shorthands need to be mitigated:
Shorthand IPIs and NMIs hit all CPUs including unplugged CPUs
Neither of those can be handled on unplugged CPUs for obvious reasons.
It would be trivial to just fully disable
On Fri, Jul 05, 2019 at 11:57:16AM +0200, Niklas Cassel wrote:
> Some Qualcomm SoCs have support for Core Power Reduction (CPR).
> On these platforms, we need to attach to the power domain provider
> providing the performance states, so that the leaky device (the CPU)
> can configure the
This patch fix some spelling typo in qos_mc_aware.sh
Signed-off-by: Masanari Iida
Acked-by: Randy Dunlap
---
tools/testing/selftests/drivers/net/mlxsw/qos_mc_aware.sh | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git
The memory allocated for the stats array may contain arbitrary data.
Signed-off-by: Andreas Schwab
---
drivers/net/phy/mscc.c | 16
1 file changed, 8 insertions(+), 8 deletions(-)
diff --git a/drivers/net/phy/mscc.c b/drivers/net/phy/mscc.c
index 28676af97b42..645d354ffb48
Em Sun, Jul 21, 2019 at 01:24:30PM +0200, Jiri Olsa escreveu:
> Moving following functions:
> cpu_map__new
> cpu_map__read
>
> under libperf with following names:
> perf_cpu_map__new
> perf_cpu_map__read
Fixed up this one:
tools/perf/arch/arm/util/cs-etm.c
> Link:
On Wed, Jul 24, 2019 at 10:36:42AM -0400, Asmaa Mnebhi wrote:
> Signed-off-by: Asmaa Mnebhi
The patch is, of course, fine, but you should add some info
about how it was found and a Reported-by: tag.
Thanks,
-corey
> ---
> drivers/char/ipmi/ipmb_dev_int.c | 2 +-
> 1 file changed, 1
On Tue, Jul 23, 2019 at 03:44:54PM +0200, Greg KH wrote:
> On Tue, Jul 23, 2019 at 03:31:32PM +0200, Thomas Gleixner wrote:
> > On Tue, 23 Jul 2019, Greg KH wrote:
> > > On Mon, Jul 15, 2019 at 01:16:48PM -0700, H.J. Lu wrote:
> > > > >
> > > >
> > > > Since building a workable kernel for
On Thu, Jun 13, 2019 at 01:27:05PM -0700, Rafael J. Wysocki wrote:
> On Wednesday, May 15, 2019 11:54:43 PM CEST Keith Busch wrote:
> > Instead of registering the hmat cache attributes in line with parsing
> > the table, save the attributes in the memory target and register them
> > after parsing
Hello
On 7/24/19 1:47 AM, Greg KH wrote:
On Tue, Jul 23, 2019 at 10:14:14AM -0500, Dan Murphy wrote:
Hello
On 7/10/19 7:08 AM, Dan Murphy wrote:
Hello
On 6/17/19 10:09 AM, Dan Murphy wrote:
Marc
On 6/10/19 11:35 AM, Dan Murphy wrote:
Bump
On 6/6/19 8:16 AM, Dan Murphy wrote:
Marc
Bump
On 22-07-19, 09:58, Jeffrey Hugo wrote:
> DT nodes should be ordered by address, then node name, and finally label.
> The msm8998 dtsi does not follow this, so clean it up by reordering the
> nodes. While we are at it, extend the addresses to be fully 32-bits wide
> so that ordering is easy to
On Thu, Jul 25, 2019 at 12:29:51AM +0900, Masanari Iida wrote:
> This patch fix some spelling typo in qos_mc_aware.sh
>
> Signed-off-by: Masanari Iida
> Acked-by: Randy Dunlap
Reviewed-by: Ido Schimmel
On Tue, Jul 16, 2019 at 11:15 PM Luca Coelho wrote:
>
> On Tue, 2019-07-16 at 10:28 -0700, Nick Desaulniers wrote:
> > On Thu, Jul 11, 2019 at 7:15 PM Joe Perches wrote:
> > > On Thu, 2019-07-11 at 17:17 -0700, Nick Desaulniers wrote:
> > > > Commit r353569 in prerelease Clang-9 is producing a
On Wed, Jul 24, 2019 at 07:55:13AM -0700, Moritz Fischer wrote:
> On Wed, Jul 24, 2019 at 09:20:56AM +0200, Greg KH wrote:
> > On Tue, Jul 23, 2019 at 10:20:12PM -0700, Moritz Fischer wrote:
> > > The following changes since commit
> > > 5f9e832c137075045d15cd6899ab0505cfb2ca4b:
> > >
> > >
Em Sun, Jul 21, 2019 at 01:24:34PM +0200, Jiri Olsa escreveu:
> Adding perf_evlist__for_each_evsel macro to iterate
> perf_evsel objects in evlist.
>
> Adding perf_evlist__next function to do that.
Replaced the above line in the cset commit log with:
Introduce the perf_evlist__next()
On Wed, Jul 24, 2019 at 08:00:42PM +0800, Haishuang Yan wrote:
> Since ip6_tnl_parse_tlv_enc_lim() can call pskb_may_pull()
> which may change skb->data, so we need to re-load ipv6h at
> the right place.
>
> Fixes: 898b29798e36 ("ip6_gre: Refactor ip6gre xmit codes")
> Cc: William Tu
>
On Wed 24-07-19 16:23:24, David Hildenbrand wrote:
> Let's remove this indirection. We need the zone in the caller either
> way, so let's just detect it there. Add some documentation for
> move_pfn_range_to_zone() instead.
>
> Cc: Andrew Morton
> Cc: Oscar Salvador
> Cc: Michal Hocko
> Cc:
Hello,
syzbot found the following crash on:
HEAD commit:abdfd52a Merge tag 'armsoc-defconfig' of git://git.kernel...
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=11be489460
kernel config: https://syzkaller.appspot.com/x/.config?x=b8e53b1e149c0183
On Wed, Jul 24, 2019 at 2:08 PM syzbot
wrote:
>
> Hello,
>
> syzbot found the following crash on:
>
> HEAD commit:abdfd52a Merge tag 'armsoc-defconfig' of git://git.kernel...
> git tree: upstream
> console output: https://syzkaller.appspot.com/x/log.txt?x=163046afa0
> kernel
On Wed, Jul 24, 2019 at 02:02:31PM +0530, Nishka Dasgupta wrote:
> The local variable search in regulator_of_get_init_node takes the value
> returned by either of_get_child_by_name or of_node_get, both of which
> get a node. If this node is not put before returning, it could cause a
> memory leak.
On 7/23/19 9:56 PM, Eric Biggers wrote:
Does this also fix any of the other bugs listed at
https://lore.kernel.org/lkml/20190710055838.GC2152@sol.localdomain/
?
BUG: MAX_LOCKDEP_CHAIN_HLOCKS too low!
BUG: MAX_LOCKDEP_CHAINS too low!
BUG: MAX_LOCK_DEPTH too low! (2)
BUG: MAX_LOCKDEP_ENTRIES too
On 24.07.19 16:23, David Hildenbrand wrote:
> Let's remove this indirection. We need the zone in the caller either
> way, so let's just detect it there. Add some documentation for
> move_pfn_range_to_zone() instead.
>
> Cc: Andrew Morton
> Cc: Oscar Salvador
> Cc: Michal Hocko
> Cc: David
On Wed, 24 Jul 2019, Greg KH wrote:
> On Tue, Jul 23, 2019 at 03:44:54PM +0200, Greg KH wrote:
> > Sorry, I saw that after writing that. You are right, if the others
> > don't object, that's fine with me. I'll go poke the various build
> > systems that are failing right now on 5.3-rc1 and try to
On 2019-07-24 12:32 a.m., Christoph Hellwig wrote:
> On Mon, Jul 22, 2019 at 05:08:52PM -0600, Logan Gunthorpe wrote:
>> diff --git a/drivers/pci/p2pdma.c b/drivers/pci/p2pdma.c
>> index 143e11d2a5c3..70c262b7c731 100644
>> --- a/drivers/pci/p2pdma.c
>> +++ b/drivers/pci/p2pdma.c
>> @@ -168,6
On Wed, Jul 24, 2019 at 04:28:31PM +0200, Jann Horn wrote:
> On Wed, Jul 24, 2019 at 12:17 AM Kees Cook wrote:
> > Perhaps we need a "statistics" counter type for these kinds of counters?
> > "counter_t"? I bet there are a lot of atomic_t uses that are just trying
> > to be counters. (likely most
On Wed, Jul 24, 2019 at 09:08:26AM +0200, Takashi Iwai wrote:
> On Wed, 24 Jul 2019 04:47:23 +0200,
> Eric Biggers wrote:
> >
> > [This email was generated by a script. Let me know if you have any
> > suggestions
> > to make it better, or if you want it re-generated with the latest status.]
> >
On Wed, Jul 24, 2019 at 05:49:45PM +0200, Thomas Gleixner wrote:
> On Wed, 24 Jul 2019, Greg KH wrote:
> > On Tue, Jul 23, 2019 at 03:44:54PM +0200, Greg KH wrote:
> > > Sorry, I saw that after writing that. You are right, if the others
> > > don't object, that's fine with me. I'll go poke the
On 2019-07-24 12:32 a.m., Christoph Hellwig wrote:
>> struct dev_pagemap *pgmap = sg_page(sg)->pgmap;
>> +struct pci_dev *client;
>> +int dist;
>> +
>> +client = find_parent_pci_dev(dev);
>> +if (WARN_ON_ONCE(!client))
>> +return 0;
>>
>> +dist =
There is a race condition between removing glue directory and adding a new
device under the glue directory. It can be reproduced in following test:
path 1: Add the child device under glue dir
device_add()
get_device_parent()
mutex_lock(_mutex);
/*find parent from
On Wed, 24 Jul 2019, Thomas Gleixner wrote:
> On Wed, 24 Jul 2019, Greg KH wrote:
> > On Tue, Jul 23, 2019 at 03:44:54PM +0200, Greg KH wrote:
> > > Sorry, I saw that after writing that. You are right, if the others
> > > don't object, that's fine with me. I'll go poke the various build
> > >
>-Original Message-
>From: Andrew Lunn
>Sent: Wednesday, July 24, 2019 6:18 PM
>To: Claudiu Manoil
>Cc: David S . Miller ; Rob Herring
>; Leo Li ; Alexandru Marginean
>; net...@vger.kernel.org;
>devicet...@vger.kernel.org; linux-arm-ker...@lists.infradead.org; linux-
On Wed, 24 Jul 2019, Greg KH wrote:
> On Wed, Jul 24, 2019 at 05:49:45PM +0200, Thomas Gleixner wrote:
> > > Ok, I dug around and the gold linker is not being used here, only clang
> > > to build the source and GNU ld to link, and I am still seeing this
> > > error.
> >
> > Odd combo.
>
> I'm
On Fri, Jul 05, 2019 at 11:57:19AM +0200, Niklas Cassel wrote:
> Add qcom-opp bindings with properties needed for Core Power Reduction
> (CPR).
>
> CPR is included in a great variety of Qualcomm SoCs, e.g. msm8916 and
> msm8996. CPR was first introduced in msm8974.
>
> Changes since RFC:
>
On Fri, 5 Jul 2019 11:57:20 +0200, Niklas Cassel wrote:
> Add DT bindings to describe the CPR HW found on certain Qualcomm SoCs.
>
> Changes since RFC:
> -Make compatible string SoC specific.
> -Changed interrupt definition.
> -Use clock binding for reference clock.
> -Clarified
On 2019-07-24 12:32 a.m., Christoph Hellwig wrote:
>> diff --git a/drivers/pci/p2pdma.c b/drivers/pci/p2pdma.c
>> index baf476039396..20c834cfd2d3 100644
>> --- a/drivers/pci/p2pdma.c
>> +++ b/drivers/pci/p2pdma.c
>> @@ -874,6 +874,91 @@ void pci_p2pdma_unmap_sg_attrs(struct device *dev,
>>
I think the atomic_pte_lookup / non_atomic_pte_lookup helpers
should simply go away. Most of the setup code is common now and should
be in the caller where it can be shared. Then just do a:
if (atomic) {
__get_user_pages_fast()
} else {
Hi Ruslan,
On Wed, Jul 10, 2019 at 03:27:58PM +0300, Ruslan Bilovol wrote:
> On Tue, Apr 9, 2019 at 8:52 PM Will Deacon wrote:
> >
> > On Mon, Apr 08, 2019 at 04:36:28PM +0100, Mark Rutland wrote:
> > > On Mon, Mar 11, 2019 at 12:49:46PM +0100, Torsten Duwe wrote:
> > > > On Wed, Feb 13, 2019 at
On Wed, Jul 24, 2019 at 06:03:41PM +0200, Thomas Gleixner wrote:
> On Wed, 24 Jul 2019, Greg KH wrote:
> > On Wed, Jul 24, 2019 at 05:49:45PM +0200, Thomas Gleixner wrote:
> > > > Ok, I dug around and the gold linker is not being used here, only clang
> > > > to build the source and GNU ld to
On Wed, Jul 24, 2019 at 05:32:57PM +0200, Andreas Schwab wrote:
> The memory allocated for the stats array may contain arbitrary data.
>
> Signed-off-by: Andreas Schwab
Reviewed-by: Andrew Lunn
Fixes: e4f9ba642f0b ("net: phy: mscc: add support for VSC8514 PHY.")
Fixes: 00d70d8e0e78 ("net: phy:
On Tue, Jul 23, 2019 at 4:54 PM Jann Horn wrote:
> On Mon, Jul 22, 2019 at 3:44 PM Ondrej Mosnacek wrote:
> > On Mon, Jul 22, 2019 at 1:35 PM NitinGote wrote:
> > > refcount_t type and corresponding API should be
> > > used instead of atomic_t when the variable is used as
> > > a reference
The linux-next commit "net: Rename skb_frag_t size to bv_len" [1]
introduced a compilation error on powerpc as it forgot to deal with the
renaming from "size" to "bv_len" for ixgbevf.
[1]
On Fri, Jul 05, 2019 at 08:44:36PM +0530, Manivannan Sadhasivam wrote:
> Add devicetree binding for Bitmain BM1880 SoC clock controller.
>
> Signed-off-by: Manivannan Sadhasivam
> ---
> .../bindings/clock/bitmain,bm1880-clk.txt | 47 +++
> include/dt-bindings/clock/bm1880-clock.h
Commit-ID: 511885d7061eda3eb1faf3f57dcc936ff75863f1
Gitweb: https://git.kernel.org/tip/511885d7061eda3eb1faf3f57dcc936ff75863f1
Author: Davidlohr Bueso
AuthorDate: Wed, 24 Jul 2019 08:23:23 -0700
Committer: Thomas Gleixner
CommitDate: Wed, 24 Jul 2019 17:38:01 +0200
lib/timerqueue:
On Sun, Jul 07, 2019 at 03:22:46PM +0200, Aleix Roca Nonell wrote:
> Add binding for Realtek RTD129x interrupt controller.
>
> Signed-off-by: Aleix Roca Nonell
> ---
> .../realtek,rtd129x-intc.txt | 24 +++
> 1 file changed, 24 insertions(+)
> create mode
On Wed, Jul 24, 2019 at 05:57:35PM +0200, Greg KH wrote:
> Wait, does clang link things itself and not need ld?
There's ld.lld; which might be used by your clang.
As explained in this previous series [0], on Amlogic, we are using codec to
codec links to deal with the glue which is between the i2s backends and the
synopsys hdmi controller.
This worked well until I tried to .get_eld() support in the dw-hdmi-i2s
driver. Doing so adds channel mapping controls
When handling dai_link events on codec to codec links, run all .startup()
callbacks on sinks and sources before running any .hw_params(). Same goes
for hw_free() and shutdown(). This is closer to the behavior of regular
dai links
Signed-off-by: Jerome Brunet
---
sound/soc/soc-dapm.c | 38
At the moment, codec to codec links uses an ephemeral variable for
the struct snd_pcm_substream. Also the struct snd_soc_pcm_runtime
does not have real struct snd_pcm.
This might a problem if the functions used by a codec on codec to
codec link expect these structures to exist, and keep on
Now that codec to codec links struct snd_soc_pcm_runtime have lasting pcm
and substreams, let's use them. Alsa allocate and keep the
struct snd_pcm_runtime as long as the link is powered.
Signed-off-by: Jerome Brunet
---
sound/soc/soc-dapm.c | 86
1
When there is an event on codec to codec dai_link, we only need to deal
with params if the event is SND_SOC_DAPM_PRE_PMU, when .hw_params() is
called. For the other events, it is useless.
Also, params does not need to be dynamically allocated as it does not
need to survive the event.
Last,
Set the information provided struct snd_soc_pcm_stream in the
struct snd_pcm_runtime of the codec to codec link.
Signed-off-by: Jerome Brunet
---
sound/soc/soc-dapm.c | 5 +
1 file changed, 5 insertions(+)
diff --git a/sound/soc/soc-dapm.c b/sound/soc/soc-dapm.c
index
At the moment, codec to codec dai link widgets are named after the
cpu dai and the 1st codec valid on the link. This might be confusing
if there is multiple valid codecs on the link for one stream
direction.
Instead, use the dai link name and the stream direction to name the
the dai link widget
On Wed, Jul 24, 2019 at 08:39:05AM +0200, Eric Dumazet wrote:
>
>
> On 7/24/19 3:38 AM, Eric Biggers wrote:
> > [This email was generated by a script. Let me know if you have any
> > suggestions
> > to make it better, or if you want it re-generated with the latest status.]
> >
> > Of the
On Sun, 7 Jul 2019 22:52:38 -0500, Suman Anna wrote:
> The Programmable Real-Time Unit Subsystem (PRUSS) contains an interrupt
> controller (INTC) that can handle various system input events and post
> interrupts back to the device-level initiators. The INTC can support
> upto 64 input events on
On 23/07/2019 10:57, Mark Rutland wrote:
> On Mon, Jul 22, 2019 at 04:42:08PM +0100, Steven Price wrote:
>> Add a generic version of page table dumping that architectures can
>> opt-in to
>>
>> Signed-off-by: Steven Price
>
> [...]
>
>> +#ifdef CONFIG_KASAN
>> +/*
>> + * This is an optimization
Hi Christophe
On 6/21/19 4:49 PM, Christophe Kerello wrote:
This patch adds FMC2 NAND controller support used by stm32mp157c SOC.
Signed-off-by: Christophe Kerello
---
arch/arm/boot/dts/stm32mp157c.dtsi | 19 +++
1 file changed, 19 insertions(+)
diff --git
> >All the horrible casts go away, the driver is structured like every
> >other driver, sparse is probably happy, etc.
> >
>
> This looks more like a matter cosmetic preferences. I mean, I didn't
> notice anything "horrible" in the code so far.
#define bus_to_enetc_regs(bus) (struct
On Wed, 2019-07-24 at 12:17 -0400, Qian Cai wrote:
> The linux-next commit "net: Rename skb_frag_t size to bv_len" [1]
> introduced a compilation error on powerpc as it forgot to deal with
> the
> renaming from "size" to "bv_len" for ixgbevf.
>
> [1]
>
Hi Olivier
On 7/5/19 1:53 PM, Olivier Moysan wrote:
Add support of Cirrus cs42l51 audio codec on stm32mp157a-dk1 board.
Configuration overview:
- SAI2A is the CPU interface used for the codec audio playback
- SAI2B is the CPU interface used for the codec audio record
- SAI2A is configured as a
On 24/07/2019 12:26, Chuhong Yuan wrote:
> Instead of using to_pci_dev + pci_get_drvdata,
> use dev_get_drvdata to make code simpler.
>
> Signed-off-by: Chuhong Yuan
Acked-by: Edward Cree
> ---
> drivers/net/ethernet/sfc/ef10.c | 4 ++--
> drivers/net/ethernet/sfc/efx.c | 10 +-
> 2
On Wed, 10 Jul 2019 12:19:00 -0500
Josh Poimboeuf wrote:
> On Wed, Jul 10, 2019 at 01:09:24PM -0400, Steven Rostedt wrote:
> >
> > Josh,
> >
> > Can you have a look at these? I can apply them if you think they are OK.
>
> Sorry for the delay. I didn't forget about it, it's just been a
On Mon, Jul 08, 2019 at 12:35:47PM +0200, Jean-Jacques Hiblot wrote:
> Most of the LEDs are powered by a voltage/current regulator. describing in
> the device-tree makes it possible for the LED core to enable/disable it
> when needed.
>
> Signed-off-by: Jean-Jacques Hiblot
> ---
>
Previously a condition got missed where the pidfd waiters are awakened
before the exit_state gets set. This can result in a missed notification
[1] and the polling thread waiting forever.
It is fixed now, however it would be nice to avoid this kind of issue
going unnoticed in the future. So just
On Tue, Jul 23, 2019 at 09:06:08PM +0800, lufe...@163.com wrote:
> From: luferry
>
> x2apic_eanbled() costs about 200 cycles
> when guest trigger halt pretty high, pi ops in hotpath
>
> Signed-off-by: luferry
> ---
> arch/x86/kvm/vmx/vmx.c | 10 +++---
> 1 file changed, 7 insertions(+), 3
On Wed, Jul 24, 2019 at 04:10:40PM +0200, Peter Zijlstra wrote:
> And that most certainly should trigger...
>
> Let me gdb that objtool thing.
---
Subject: objtool: Improve UACCESS coverage
A clang build reported an (obvious) double CLAC while a GCC build did
not; it turns out we only re-visit
On Tue, Jul 23, 2019 at 09:43:24PM -0500, Josh Poimboeuf wrote:
> On Thu, Jul 18, 2019 at 10:40:09PM +0200, Thomas Gleixner wrote:
>
> > drivers/gpu/drm/i915/gem/i915_gem_execbuffer.o: warning: objtool:
> > .altinstr_replacement+0x86: redundant UACCESS disable
>
> Looking at this one, I think
On Wed, Jul 24, 2019 at 04:05:17AM -0400, Michael S. Tsirkin wrote:
> On Wed, Jul 24, 2019 at 10:17:14AM +0800, Jason Wang wrote:
> > So even PTE is read speculatively before reading invalidate_count (only in
> > the case of invalidate_count is zero). The spinlock has guaranteed that we
> > won't
On July 24, 2019 6:48:16 PM GMT+02:00, "Joel Fernandes (Google)"
wrote:
>Previously a condition got missed where the pidfd waiters are awakened
>before the exit_state gets set. This can result in a missed
>notification
>[1] and the polling thread waiting forever.
>
>It is fixed now, however it
401 - 500 of 2064 matches
Mail list logo
