From: John Ogness
Date: Thu, 13 Aug 2020 21:45:25 +0206
> After @blk_fill_in_prog_lock is acquired there is an early out vnet
> situation that can occur. In that case, the rwlock needs to be
> released.
>
> Also, since @blk_fill_in_prog_lock is only acquired when @tp_version
> is exactly
Lieber Freund,
Ich bin Herr Tayeb Souami, New Jersey, Vereinigte Staaten von Amerika,
der Mega-Gewinner von $ 315million In Mega Millions Jackpot, spende ich
an 5 zufällige Personen, wenn Sie diese E-Mail erhalten, dann wurde Ihre
E-Mail nach einem Spinball ausgewählt.Ich habe den größten Teil
From: Steven Rostedt (VMware)
While reviewing some patches for bootconfig, I noticed the following
code in xbc_node_compose_key_after():
ret = snprintf(buf, size, "%s%s", xbc_node_get_data(node),
depth ? "." : "");
if (ret < 0)
return ret;
On 13/08/20 20:16, Ingo Molnar wrote:
> * Valentin Schneider wrote:
>
>> The ARM-specific GMC level is meant to be built using the thread sibling
>> mask, but no devicetree in arch/arm/boot/dts uses the 'thread' cpu-map
>> binding. With SD_SHARE_POWERDOMAIN gone, this topology level can be
>>
Static analyzer showed following the code path at
tools/bpf/bpftool/main.c:308 leads to returning err when uninitialized
if (n_argc < 0)
goto err_close;
Initializing err to -1 fixes the uninitialized return and prevents
having to add a 3rd err = -1 line.
On Fri, Jul 03, 2020 at 10:44:16AM +0300, Eugen Hristev wrote:
> Add Microchip CSI2DC driver in the list.
>
> Signed-off-by: Eugen Hristev
The MAINTAINERS change should be no later than the files. I guess it could
be part of another patch as well.
--
Sakari Ailus
Hi Eugen,
On Fri, Jul 03, 2020 at 10:44:12AM +0300, Eugen Hristev wrote:
> Hi,
>
> This series adds support for the Microchip csi2dc csi-2 demux controller.
>
> I was not fully sure where is the best place for such a helper chip, thus
> I added the driver in a separate 'misc' menu under the
These changes take advantage of the new capability added in
merge commit 00e4db51259a5f936fec1424b884f029479d3981
"Allow using computed metrics in calculating other metrics".
The net is a simplification of the expressions for a handful
of metrics, but no functional change.
Signed-off-by: Paul A.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: dddcbc139e96bd18d8c65ef7b7e440f0d32457c2
commit: 76d7728db724466490c2c3dd4f84c3357f550615 crypto/chcr: IPV6 code needs
to be in CONFIG_IPV6
date: 2 months ago
config: ia64-randconfig-r033-20200814
Doug,
On Thu, Aug 13 2020 at 09:09, Doug Anderson wrote:
> On Thu, Aug 13, 2020 at 2:29 AM Thomas Gleixner wrote:
>> The main point is that these callbacks are specific to generic chip and
>> not used anywhere else.
>
> I'm not sure I understand. This callback is used by drivers that use
>
Hello,
This series adds initial support for the DRM bridges to NVIDIA Tegra DRM
driver. This is required by newer device-trees where we model the LVDS
encoder bridge properly. In particular this series is needed in order to
light up display panels of recently merged Acer A500 and Nexus 7 devices.
Newer Tegra device-trees will specify a video output graph, which involves
LVDS encoder bridge. This patch adds support for the LVDS encoder bridge
to the RGB output, allowing us to model the display hardware properly.
Reviewed-by: Laurent Pinchart
Acked-by: Sam Ravnborg
Signed-off-by: Dmitry
Hi all,
In commit
14dee0586104 ("drm/xen-front: Fix misused IS_ERR_OR_NULL checks")
Fixes tag
Fixes: c575b7eeb89f: "drm/xen-front: Add support for Xen PV display frontend"
has these problem(s):
- missing space between the SHA1 and the subject
- Subject does not match target commit
The OF node should be put before returning error in tegra_output_probe(),
otherwise node's refcount will be leaked.
Reviewed-by: Laurent Pinchart
Reviewed-by: Sam Ravnborg
Signed-off-by: Dmitry Osipenko
---
drivers/gpu/drm/tegra/output.c | 9 -
1 file changed, 4 insertions(+), 5
Newer Tegra device-trees will specify a video output graph which involves
a bridge. This patch adds initial support for the DRM bridges to the Tegra
DRM output.
Acked-by: Sam Ravnborg
Signed-off-by: Dmitry Osipenko
---
drivers/gpu/drm/tegra/drm.h| 2 ++
drivers/gpu/drm/tegra/output.c | 12
Currently Tegra DRM driver manually manages display panel, but this
management could be moved out into DRM core if we'll wrap panel into
DRM bridge. This patch wraps RGB panel into a DRM bridge and removes
manual handling of the panel from the RGB output code.
Suggested-by: Laurent Pinchart
On Thu, Aug 13, 2020 at 11:52:57AM -0700, Paul E. McKenney wrote:
> On Thu, Aug 13, 2020 at 08:26:18PM +0200, pet...@infradead.org wrote:
> > I thought the rule was:
> >
> > - No allocators (alloc/free) inside raw_spinlock_t, full-stop.
> >
> > Why are we trying to craft an exception?
>
> So
On Thu, Aug 13, 2020 at 3:04 AM Brian Starkey wrote:
> On Sat, Jul 25, 2020 at 03:26:33AM +, John Stultz wrote:
> > Add proper refcounting on the dma_heap structure.
> > While existing heaps are built-in, we may eventually
> > have heaps loaded from modules, and we'll need to be
> > able to
Hi Sowjanya,
On Fri, Jul 31, 2020 at 09:34:15AM -0700, Sowjanya Komatineni wrote:
>
> On 7/31/20 9:26 AM, Sakari Ailus wrote:
> > Hi Sowjanya,
> >
> > Thanks for the patch.
> >
> > On Mon, Jul 20, 2020 at 10:01:34AM -0700, Sowjanya Komatineni wrote:
> > > IMX274 has VANA analog 2.8V supply,
The panel orientation needs to parsed from a device-tree and assigned to
the panel's connector in order to make orientation property available to
userspace. That's what this patch does for the panel-simple driver.
Signed-off-by: Dmitry Osipenko
---
drivers/gpu/drm/panel/panel-simple.c | 11
Hello!
This series adds support for display panel's DT rotation property. It's a
continuation of the work that was initially started by Derek Basehore for
the panel driver that is used by some Mediatek device [1]. I picked up the
Derek's patches and added my t-b and r-b tags to them, I also added
From: Derek Basehore
This reads the DT setting for the panel rotation to set the panel
orientation in the get_modes callback.
Reviewed-by: Dmitry Osipenko
Signed-off-by: Derek Basehore
Signed-off-by: Dmitry Osipenko
---
drivers/gpu/drm/panel/panel-boe-tv101wum-nl6.c | 6 ++
1 file
From: Derek Basehore
This adds a helper function for reading the rotation (panel
orientation) from the device tree.
Reviewed-by: Sam Ravnborg
Tested-by: Dmitry Osipenko
Signed-off-by: Derek Basehore
Signed-off-by: Dmitry Osipenko
---
drivers/gpu/drm/drm_panel.c | 43
The panel orientation needs to parsed from a device-tree and assigned to
the panel's connector in order to make orientation property available to
userspace. That's what this patch does for the generic LVDS panel.
Signed-off-by: Dmitry Osipenko
---
drivers/gpu/drm/panel/panel-lvds.c | 10
Hi Kieran,
On Thu, Aug 13, 2020 at 08:01:01PM +0100, Kieran Bingham wrote:
> Hi Randy,
>
> On 13/08/2020 19:35, Randy Dunlap wrote:
> > On 8/12/20 11:58 PM, Stephen Rothwell wrote:
> >> Hi all,
> >>
> >> News: The merge window has opened, so please do not add any v5.10
> >> related material to
On Wed, Aug 05, 2020 at 02:51:13PM +0200, Jacopo Mondi wrote:
> Hi Paul,
>
> On Mon, Aug 03, 2020 at 11:06:58AM +0200, Paul Kocialkowski wrote:
> > Although the code is correct and doing the right thing, the clock diagram
> > showed the wrong register for the bit divider, which had me doubting
On Tue, Jul 28, 2020 at 12:14:31PM +0900, Masahisa Kojima wrote:
> When fitted, the SynQuacer platform exposes its SPI TPM via a MMIO
> window that is backed by the SPI command sequencer in the SPI bus
> controller. This arrangement has the limitation that only byte size
> accesses are supported,
why not simply use nanosleep(2)
On Tue, Mar 31, 2020 at 2:45 PM Chen Yu wrote:
>
> Since the RAPL Joule Counter is 32 bit, turbostat would
> only print a *star* instead of printing the actual energy
> consumed to indicate the overflow due to long duration.
> This does not meet the requirement
On Thu, 13 Aug 2020 14:37:03 -0700
Peiyong Lin wrote:
> Historically there is no common trace event for GPU frequency, in
> downstream Android each different hardware vendor implements their own
> way to expose GPU frequency, for example as a debugfs node. This patch
> standardize it as a
On Mon, Jul 27, 2020 at 12:13:44PM +0900, Masahisa Kojima wrote:
> Hi Jarkko,
>
> Thank you for your comments.
>
> On Thu, 23 Jul 2020 at 11:36, Jarkko Sakkinen
> wrote:
> >
> > On Fri, Jul 17, 2020 at 05:49:31PM +0900, Masahisa Kojima wrote:
> > > When fitted, the SynQuacer platform exposes
Huh?
On Fri, Jul 17, 2020 at 2:09 AM Liwei Song wrote:
>
> with 32-bit rootfs, the offset may out of range when set it
> to 0xc0010299, define it as "unsigned long long" type and
> call pread64 directly in kernel.
>
> Signed-off-by: Liwei Song
> ---
> tools/power/x86/turbostat/turbostat.c | 5
On Thu, Aug 13, 2020 at 12:41 PM Arnd Bergmann wrote:
>
> On Tue, Aug 4, 2020 at 11:26 PM Daniel Gutson wrote:
> > On Tue, Aug 4, 2020 at 5:46 PM Arnd Bergmann wrote:
> > > > But wait, Mika, the author of the file, asked earlier not to remove
> > > > the module parameter of intel-spi, and just
Hi Suraj,
Thanks for the patch.
On Sat, Jul 18, 2020 at 07:02:38PM +0530, Suraj Upadhyay wrote:
> Replace depracated psi_enable_msi with pci_alloc_irq_vectors.
> And as a result modify how the returned value is handled.
>
> Signed-off-by: Suraj Upadhyay
> ---
>
Historically there is no common trace event for GPU frequency, in
downstream Android each different hardware vendor implements their own
way to expose GPU frequency, for example as a debugfs node. This patch
standardize it as a common trace event in upstream linux kernel to help
the ecosystem
On Wed, Aug 12, 2020 at 10:29:56PM -0700, Jay Vosburgh wrote:
> Did you notice this by inspection, or did it come up in use
> somewhere? I can't recall ever hearing of anyone using broadcast mode,
> so I'm curious if there is a use for it, but this change seems
> reasonable enough
From: David Heidelberg
SMB345 tested on Nexus 7 2013.
Based on:
- https://patchwork.kernel.org/patch/4922431/
- https://patchwork.ozlabs.org/patch/666877/
Signed-off-by: David Heidelberg
---
drivers/power/supply/Kconfig | 6 +-
drivers/power/supply/smb347-charger.c | 109
From: David Heidelberg
Add SMB345 charger node to Nexus 7 2013 DTS.
Proper charger configuration prevents battery from overcharging.
Original author: Vinay Simha BN
Signed-off-by: David Heidelberg
---
.../boot/dts/qcom-apq8064-asus-nexus7-flo.dts | 24 +++
1 file changed, 24
The generic battery temperature properties are already supported by the
power-supply core. Let's support parsing of the common battery temperature
properties from a device-tree.
Signed-off-by: Dmitry Osipenko
---
drivers/power/supply/power_supply_core.c | 19 +++
From: David Heidelberg
SMB347 is a battery charger controller which is found on the Nexus 7
device.
Signed-off-by: David Heidelberg
Signed-off-by: Dmitry Osipenko
---
.../tegra30-asus-nexus7-grouper-common.dtsi | 24 ++-
1 file changed, 23 insertions(+), 1 deletion(-)
diff
From: David Heidelberg
This patch adds device-tree support to the SMB347 charger driver. All
legacy platform data now can be parsed from DT. Because of that and since
SMB347 is an I2C client driver, the IRQ number can be passed automatically
through client's IRQ variable if it's defined in DT.
From: David Heidelberg
SMB347 is a charger and not a battery driver. Secondly, power-supply core
now supports monitored-battery. So the 'fake' battery doesn't do anything
useful for us, and thus, it should be removed.
Transfer smb347-battery functionality into smb347-mains and smb347-usb.
We gathered existing patches, fixed and improved what we could and
final result is an working charging driver with device-tree support
for Nexus 7.
At this moment charging works with:
- Nexus 7 2012 (grouper and tilapia)
- Nexus 7 2013 (flo and deb)
- ... and there are more devices equipped
Document generic battery temperature properties.
Signed-off-by: Dmitry Osipenko
---
.../bindings/power/supply/battery.yaml| 24 +++
1 file changed, 24 insertions(+)
diff --git a/Documentation/devicetree/bindings/power/supply/battery.yaml
Let's simply disable/enable IRQ rather than use a mutex that protects from
racing with the interrupt handler. The result of this patch is that it's a
bit easier now to follow the driver's code.
Tested-by: David Heidelberg
Signed-off-by: Dmitry Osipenko
---
drivers/power/supply/smb347-charger.c
From: David Heidelberg
Summit SMB3xx series is a Programmable Switching Li+ Battery Charger.
This patch adds device-tree binding for Summit SMB345, SMB347 and SMB358
chargers.
Signed-off-by: David Heidelberg
Signed-off-by: Dmitry Osipenko
---
.../power/supply/summit,smb347-charger.yaml |
From: David Heidelberg
Simplify code, more convenient to use with Device Tree.
Reviewed-by: Dmitry Osipenko
Signed-off-by: David Heidelberg
---
drivers/power/supply/smb347-charger.c | 75 +++
1 file changed, 29 insertions(+), 46 deletions(-)
diff --git
On 8/13/20 5:10 PM, David Laight wrote:
From: Josef Bacik
Sent: 13 August 2020 18:19
...
We wouldn't even need the extra +1 part, since we're only copying in how much
the user wants anyway, we could just go ahead and convert this to
left -= snprintf(buffer, left, "0x%04x\n", *(unsigned int
On Thu, 13 Aug 2020 14:03:57 -0700
Peiyong Lin wrote:
> +/**
> + * gpu_frequency - Reports frequency changes in GPU clock domains
> + * @state: New frequency (in KHz)
> + * @gpu_id: GPU clock domain
> + */
> +TRACE_EVENT(gpu_frequency,
> +
> + TP_PROTO(unsigned int state, unsigned int
This driver doesn't use the id information provided by the old i2c
probe function, so it can trivially be converted to the simple
("probe_new") form.
Signed-off-by: Stephen Kitt
---
drivers/hwmon/ltc2947-i2c.c | 5 ++---
1 file changed, 2 insertions(+), 3 deletions(-)
diff --git
Applied.
thanks!
-Len
On Thu, Mar 26, 2020 at 4:36 PM Doug Smythies wrote:
>
> If the --quiet option is not used, turbostat prints a useful system
> configuration header during startup. Inclusion of idle system configuration
> information is a function of inclusion in the columns choosen to be
From: Josef Bacik
> Sent: 13 August 2020 18:19
...
> We wouldn't even need the extra +1 part, since we're only copying in how much
> the user wants anyway, we could just go ahead and convert this to
>
> left -= snprintf(buffer, left, "0x%04x\n", *(unsigned int *) table->data);
>
> and be fine,
Linus,
likely because of the holiday season, the I2C pull request is quite smaller
this time. Main features:
* bus recovery can now be given a pinctrl handle and the I2C core will
do all the steps to switch to/from GPIO which can save quite some
boilerplate code from drivers
* "fallthrough"
The buffer coming from higher up the stack has an extra byte to handle
the NULL terminator in the string. Instead of using a temporary buffer
to sprintf into and then copying into the buffer, just scnprintf
directly into the buffer and update lenp as appropriate.
Signed-off-by: Josef Bacik
---
Now that we're allocating an extra slot for the NULL terminated string,
use scnprintf() and write directly into the buffer.
Signed-off-by: Josef Bacik
---
net/sunrpc/sysctl.c| 10 ++
net/sunrpc/xprtrdma/svc_rdma.c | 16 ++--
2 files changed, 4 insertions(+), 22
Now that we're passing down a kernel buffer with enough space to account
for an extra NULL terminator, go ahead and use scnprintf() to print out
a long in proc_put_long(). count here includes NULL terminator slot in
the buffer, so we will get the correct behavior we're looking for.
Historically there is no common trace event for GPU frequency, in
downstream Android each different hardware vendor implements their own
way to expose GPU frequency, for example as a debugfs node. This patch
standardize it as a common trace event in upstream linux kernel to help
the ecosystem
This initialy started with
[PATCH 1/6] proc: use vmalloc for our kernel buffer
Which came about because we were getting page alloc failures when cat tried to
do a read with a 64kib buffer, triggering an order 4 allocation. We need to
switch to kvmalloc for this buffer to avoid these high
Since
sysctl: pass kernel pointers to ->proc_handler
we have been pre-allocating a buffer to copy the data from the proc
handlers into, and then copying that to userspace. The problem is this
just blind kmalloc()'s the buffer size passed in from the read, which in
the case of our 'cat' binary
Al suggested that if we allocate enough space to add in the '\0'
character at the end of our strings, we could just use scnprintf() in
our ->proc_handler functions without having to be fancy about keeping
track of space. There are a lot of these handlers, so the follow ups
will be separate, but
This helper uses kvmalloc, not vmalloc, so rename it to kvmemdup_user to
make it clear we're using kvmalloc() and will need to use kvfree().
Signed-off-by: Josef Bacik
---
arch/x86/kvm/cpuid.c | 6 +++---
drivers/gpu/drm/virtio/virtgpu_ioctl.c | 2 +-
On Thu, Aug 13, 2020 at 08:59:22PM +0800, Qi Liu wrote:
> Add ETMv4 periperhal ID for HiSilicon Hip08 and Hip09 platform. Hip08
> contains ETMv4.2 device and Hip09 contains ETMv4.5 device.
>
> Signed-off-by: Qi Liu
I have applied your patch to my local branch - it will be published on Monday
The pull request you sent on Thu, 13 Aug 2020 14:52:07 -0600:
> git://git.lwn.net/linux.git tags/docs-5.9-2
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/dddcbc139e96bd18d8c65ef7b7e440f0d32457c2
Thank you!
--
Deet-doot-dot, I am a bot.
Adds an API to allow dynamic analysis tools to fail the currently
running KUnit test case.
- Always places the kunit test in the task_struct to allow other tools
to access the currently running KUnit test.
- Creates a new header file to avoid circular dependencies that could be
created from the
Integrates UBSAN into the KUnit testing framework. It fails KUnit tests
whenever it reports undefined behavior.
Signed-off-by: Uriel Guajardo
---
lib/ubsan.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/lib/ubsan.c b/lib/ubsan.c
index cb9af3f6b77e..1460e2c828c8 100644
--- a/lib/ubsan.c
On Thu, Aug 13, 2020 at 12:04:55PM +0200, Mian Yousaf Kaukab wrote:
> Since port-numbers start from 0, add 1 to port-number to get the port
> count.
>
> Fix following crash when Coresight is enabled on ACPI based systems:
>
> [ 61.061736] Unable to handle kernel NULL pointer dereference at
On Thu, Aug 13, 2020 at 11:31 PM Arjan van de Ven wrote:
> On 8/13/2020 12:58 PM, Randy Dunlap wrote:
> > From: Randy Dunlap
> >
> > Fix build error when CONFIG_ACPI is not set/enabled by adding
> > the header file which contains a stub for the function
> > in the build error.
> >
> >
On 8/7/2020 11:17 AM, Florian Fainelli wrote:
On 8/7/2020 6:14 AM, Greg KH wrote:
On Thu, Aug 06, 2020 at 01:00:54PM -0700, Florian Fainelli wrote:
On 7/20/2020 11:26 AM, Florian Fainelli wrote:
On 7/20/20 6:04 AM, Greg KH wrote:
On Thu, Jul 09, 2020 at 12:50:23PM -0700, Florian
The following changes since commit
2c12c8103d8f15790cf880f1545dafa36acb004a:
scripts/kernel-doc: optionally treat warnings as errors (2020-07-31 11:11:17
-0600)
are available in the Git repository at:
git://git.lwn.net/linux.git tags/docs-5.9-2
for you to fetch changes up to
Many hwmon drivers don't use the id information provided by the old
i2c probe function, and the remainder can easily be adapted to the new
form ("probe_new") by calling i2c_match_id explicitly.
This avoids scanning the identifier tables during probes.
Drivers which didn't use the id are
The following commit has been merged into the locking/urgent branch of tip:
Commit-ID: cb75c95c5262328bd4da3dd334f6826a3a34a979
Gitweb:
https://git.kernel.org/tip/cb75c95c5262328bd4da3dd334f6826a3a34a979
Author:Huang Shijie
AuthorDate:Thu, 13 Aug 2020 14:02:20 +08:00
The following commit has been merged into the locking/urgent branch of tip:
Commit-ID: 405fa8ac89e7aaa87282df659e525992f2639e76
Gitweb:
https://git.kernel.org/tip/405fa8ac89e7aaa87282df659e525992f2639e76
Author:Miaohe Lin
AuthorDate:Thu, 13 Aug 2020 08:21:17 -04:00
On Mon, Aug 10, 2020 at 3:43 PM Brendan Higgins
wrote:
>
> On Thu, Aug 6, 2020 at 10:43 AM Uriel Guajardo
> wrote:
> >
> > Integrates UBSAN into the KUnit testing framework. It fails KUnit tests
> > whenever it reports undefined behavior.
> >
> > Signed-off-by: Uriel Guajardo
>
> You should
On Thu, 13 Aug 2020 14:02:20 +0800
Huang Shijie wrote:
> We have three categories locks, not two.
>
> Signed-off-by: Huang Shijie
> ---
> Documentation/locking/locktypes.rst | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/locking/locktypes.rst
>
t
>
> arch/x86/pci/intel_mid_pci.c |1 +
> 1 file changed, 1 insertion(+)
>
> --- linux-next-20200813.orig/arch/x86/pci/intel_mid_pci.c
> +++ linux-next-20200813/arch/x86/pci/intel_mid_pci.c
> @@ -33,6 +33,7 @@
> #include
> #include
> #include
> +#include
>
Instruction dump uses two printk() in a row to print one instruction. Use
KERN_CONT to prevent breaking the output in the middle.
Signed-off-by: Łukasz Stelmach
---
drivers/dma/pl330.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/dma/pl330.c b/drivers/dma/pl330.c
On Mon, 10 Aug 2020, Ben Levinsky wrote:
> R5 is included in Xilinx Zynq UltraScale MPSoC so by adding this
> remotproc driver, we can boot the R5 sub-system in different
> configurations.
Which different configurations? How can you boot them?
> Signed-off-by: Ben Levinsky
> Signed-off-by:
On Mon, 10 Aug 2020, Ben Levinsky wrote:
> Add shutdown/wakeup a resource eemi operations to shutdown
> or bringup a resource.
>
> Signed-off-by: Ben Levinsky
> ---
> v3:
> - add xilinx-related platform mgmt fn's instead of wrapping around
> function pointer in xilinx eemi ops struct
> - fix
On Mon, 10 Aug 2020, Ben Levinsky wrote:
> This patch adds APIs to provide access and a configuration interface
> to the current power state of a sub-system on Zynqmp sub-system.
This doesn't read correctly
> Signed-off-by: Ben Levinsky
> ---
> v3:
> - add xilinx-related platform mgmt fn's
Arnd and Michael, what do you think about these new syscalls?
On 02/08/2020 23:58, Mickaël Salaün wrote:
> These 4 system calls are designed to be used by unprivileged processes
> to sandbox themselves:
> * landlock_get_features(2): Gets the supported features (required for
> backward and
On 8/13/2020 12:58 PM, Randy Dunlap wrote:
From: Randy Dunlap
Fix build error when CONFIG_ACPI is not set/enabled by adding
the header file which contains a stub for the function
in the build error.
../arch/x86/pci/intel_mid_pci.c: In function ‘intel_mid_pci_init’:
; ---
> Found in linux-next, but applies to/exists in mainline also.
>
> Alternative.1: X86_INTEL_MID depends on ACPI
> Alternative.2: drop X86_INTEL_MID support
>
> arch/x86/pci/intel_mid_pci.c |1 +
> 1 file changed, 1 insertion(+)
>
> --- linux-next-20200813.orig/arch/x
Quoting Amit Sunil Dhamne (2020-08-03 23:44:15)
> diff --git a/drivers/clk/zynqmp/clkc.c b/drivers/clk/zynqmp/clkc.c
> index db8d0d7..d813c34 100644
> --- a/drivers/clk/zynqmp/clkc.c
> +++ b/drivers/clk/zynqmp/clkc.c
> @@ -271,6 +271,33 @@ static int zynqmp_pm_clock_get_topology(u32 clock_id,
>
On Thu, Aug 06, 2020 at 02:35:11PM +0200, Peter Zijlstra wrote:
> By using lockdep_assert_*() from seqlock.h, the spaghetti monster
> attacked.
>
> Attack back by reducing seqlock.h dependencies from two key high level
> headers:
>
> - : -Remove
> - : -Remove
vfree() is being called on paged buffer allocated
using alloc_page() and mapped using vmap().
Freeing of pages in vfree() relies on nr_pages of
struct vm_struct. vmap() does not update nr_pages.
It can lead to memory leaks.
Fixes: ddaf29fd9bb6 ("firmware: Free temporary page table after
, but applies to/exists in mainline also.
Alternative.1: X86_INTEL_MID depends on ACPI
Alternative.2: drop X86_INTEL_MID support
arch/x86/pci/intel_mid_pci.c |1 +
1 file changed, 1 insertion(+)
--- linux-next-20200813.orig/arch/x86/pci/intel_mid_pci.c
+++ linux-next-20200813/arch/x86/pci
On 8/13/2020 6:28 PM, Takashi Iwai wrote:
On Wed, 12 Aug 2020 21:00:19 +0200,
Prateek Sood wrote:
vfree() is being called on paged buffer allocated
using alloc_page() and mapped using vmap().
Freeing of pages in vfree() relies on nr_pages of
struct vm_struct. vmap() does not update nr_pages.
The pull request you sent on Thu, 13 Aug 2020 19:10:43 +0200:
> git://git.kernel.org/pub/scm/linux/kernel/git/s390/linux.git tags/s390-5.9-2
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/990f227371a400c0fbcb98b75c91a7dbd65f6132
Thank you!
--
Deet-doot-dot, I am a
The pull request you sent on Thu, 13 Aug 2020 10:28:34 +0900:
> git://git.kernel.org/pub/scm/linux/kernel/git/linkinjeon/exfat.git
> tags/exfat-for-5.9-rc1
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/ff419b61fd66dab6ad223e044d1c3c54bb5cef6c
Thank you!
--
The pull request you sent on Thu, 13 Aug 2020 15:52:05 +0200:
> git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux.git for-5.9-tag
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/23c2c8c6fa325939f95d840f54bfdec3cb76906c
Thank you!
--
Deet-doot-dot, I am a
The pull request you sent on Wed, 12 Aug 2020 19:16:24 -0700:
> git://git.kernel.org/pub/scm/fs/xfs/xfs-linux.git tags/xfs-5.9-merge-8
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/69307ade14de7d9e9b14961ae7a6168e7165b6ab
Thank you!
--
Deet-doot-dot, I am a bot.
Hi Sumit.
On Tue, Aug 11, 2020 at 11:51:07PM +0530, Sumit Semwal wrote:
> Some Poco F1 phones have an LCD panel from Tianma, model nt36672a,
> with a resolution of 1080x2246 that operates in DSI video mode.
>
> Add the drm panel driver for it.
>
> During testing, Benni Steini helped us fix
>
randconfig-a005-20200811
x86_64 randconfig-a004-20200811
x86_64 randconfig-a002-20200811
i386 randconfig-a005-20200813
i386 randconfig-a001-20200813
i386 randconfig-a002-20200813
i386 randconfig
On Thu, Aug 13, 2020 at 4:12 PM Crt Mori wrote:
> On Thu, 13 Aug 2020 at 13:01, Andy Shevchenko
> wrote:
> > On Thu, Aug 13, 2020 at 10:53 AM Crt Mori wrote:
...
> > > -#define MLX90632_REF_1212LL /**< ResCtrlRef value of Ch
> > > 1 or Ch 2 */
> > > -#define MLX90632_REF_3
On Thu, Aug 13, 2020 at 4:04 PM Crt Mori wrote:
> On Thu, 13 Aug 2020 at 13:24, Andy Shevchenko
> wrote:
> > On Thu, Aug 13, 2020 at 2:14 PM Crt Mori wrote:
> > > On Thu, 13 Aug 2020 at 13:03, Andy Shevchenko
> > > wrote:
> > > > On Thu, Aug 13, 2020 at 10:53 AM Crt Mori wrote:
...
> > >
Hi Heikki,
Sure. Same as the other patch I will try to address your question here
and will update the commit description once you are satisfied with the
description.
Subject:
During PR_SWAP, source caps should be sent only after tSwapSourceStart
Commit description:
The patch addresses the
After @blk_fill_in_prog_lock is acquired there is an early out vnet
situation that can occur. In that case, the rwlock needs to be
released.
Also, since @blk_fill_in_prog_lock is only acquired when @tp_version
is exactly TPACKET_V3, only release it on that exact condition as
well.
And finally,
On Thu, Aug 13, 2020 at 12:30 PM Ingo Molnar wrote:
>
> Would be tentatively scheduled for v5.10 though, we've had enough
> excitement in this area for v5.9 I think. :-/
I think I can take it for 5.9 again if you send a pull request my way.
If it causes any other problems, we'll obviously
ago
config: x86_64-randconfig-m001-20200813 (attached as .config)
compiler: gcc-9 (Debian 9.3.0-15) 9.3.0
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot
New smatch warnings:
drivers/greybus/es2.c:439 message_send() error: double unlocked
'es2
On Tue, Aug 11, 2020 at 08:16:54AM -0700, Andy Lutomirski wrote:
>
> > On Aug 10, 2020, at 5:52 PM, Andy Lutomirski wrote:
> >
> >
> >>> On Aug 10, 2020, at 4:48 PM, Sean Christopherson
> >>> wrote:
> >>>
> >>> On Mon, Aug 10, 2020 at 04:08:46PM -0700, Andy Lutomirski wrote:
> >>> What am
On 8/12/20 7:57 AM, Randy Dunlap wrote:
> On 8/11/20 9:22 PM, Stephen Rothwell wrote:
>> Hi all,
>>
>
>
> on x86_64:
>
> ../arch/x86/pci/xen.c: In function ‘pci_xen_init’:
> ../arch/x86/pci/xen.c:410:2: error: implicit declaration of function
> ‘acpi_noirq_set’; did you mean ‘acpi_irq_get’?
>
201 - 300 of 937 matches
Mail list logo
