On 7/28/20 2:44 AM, Arnd Bergmann wrote:
On Mon, Jul 27, 2020 at 11:10 PM Suman Anna wrote:
The DT node full name is currently being used in regmap_config
which in turn is used to create the regmap debugfs directories.
This name however is not guaranteed to be unique and the regmap
debugfs
On Tue, Jul 28, 2020 at 05:26:29PM +0200, Paul Cercueil wrote:
> The driver only uses the registers up to offset 0x54. Since the EFUSE
> registers are in the middle of the NEMC registers, we only request
> the registers we will use for now - that way the EFUSE driver can
> probe too.
>
>
On 28/07/2020 17:18, Helen Koike wrote:
> Hi Hans,
>
> On 7/21/20 7:37 AM, Hans Verkuil wrote:
>> On 17/07/2020 13:54, Helen Koike wrote:
>>>
>>> +/**
>>> + * struct v4l2_plane_ext_pix_format - additional, per-plane format
>>> definition
>>> + * @sizeimage: maximum size in bytes
On Tue, Jul 28, 2020 at 03:19:00PM +0200, Markus Elfring wrote:
> > in case of an error tty_register_device_attr() returns ERR_PTR(),
> > add IS_ERR() check
>
> I suggest to improve this change description a bit.
>
> Will the tag “Fixes” become helpful for the commit message?
>
>
> …
> > +++
Hi Maxime
On Wed, 8 Jul 2020 at 18:44, Maxime Ripard wrote:
>
> The BCM2711 has a reworked display pipeline, and the load tracker needs
> some adjustement to operate properly. Let's add a compatible for BCM2711
s/adjustement/adjustment
> and disable the load tracker until properly supported.
>
On Tue, 28 Jul 2020 14:52:52 +0200
pet...@infradead.org wrote:
> On Fri, Jul 24, 2020 at 11:33:25AM -0600, Jonathan Corbet wrote:
>
> > I'm not sure what to do other than to continue to push for minimal use of
> > intrusive markup.
>
> Perhaps make it clearer in:
>
>
On 7/9/2020 10:57 PM, Bjorn Andersson wrote:
> On Thu 09 Jul 08:50 PDT 2020, Laurentiu Tudor wrote:
>
>>
>>
>> On 7/9/2020 8:01 AM, Bjorn Andersson wrote:
>>> With many Qualcomm platforms not having functional S2CR BYPASS a
>>> temporary IOMMU domain, without translation, needs to be allocated
On Sun, Jul 26, 2020 at 9:07 AM Sivaprakash Murugesan
wrote:
>
> From: Sivaprakash Murugesan
>
> Convert QCOM pci bindings to YAML schema
>
> Signed-off-by: Sivaprakash Murugesan
> ---
> [v2]
> - Referenced pci-bus.yaml
> - removed duplicate properties already referenced by pci-bus.yaml
>
On Tue, Jul 28, 2020 at 11:17:03AM -0400, Sasha Levin wrote:
> On Tue, Jul 28, 2020 at 08:56:41PM +0800, Muchun Song wrote:
> > On Mon, Jul 27, 2020 at 10:12 PM Greg Kroah-Hartman
> > wrote:
> > >
> > > From: Muchun Song
> > >
> > > commit d38a2b7a9c939e6d7329ab92b96559ccebf7b135 upstream.
> >
If the operation mode is non-zero and an external reference voltage is set,
first the operation mode is written to the advanced configuration register,
followed by the externel reference enable bit,
resetting the configuration mode to 0.
To fix this, first compose the value of the advanced
The driver only uses the registers up to offset 0x54. Since the EFUSE
registers are in the middle of the NEMC registers, we only request
the registers we will use for now - that way the EFUSE driver can
probe too.
Tested-by: H. Nikolaus Schaller
Signed-off-by: Paul Cercueil
---
Notes:
v2:
From: Alexander Usyskin
Some of the device heads are not generic and have
specific purpose, we need to announce it to the user space
so it can detect and correct device node via matching
attributes.
Generic devices are marked as 'mei' while special
purpose their own names. Currently we are
[AMD Official Use Only - Internal Distribution Only]
-Original Message-
From: Pierre-Louis Bossart
Sent: Tuesday, July 28, 2020 5:48 PM
To: Mark Brown ; RAVULAPATI, VISHNU VARDHAN RAO
Cc: moderated list:SOUND - SOC LAYER / DYNAMIC AUDIO POWER MANAGEM...
; Arnd Bergmann ; Liam Girdwood
On Fri, Jul 24, 2020 at 5:15 AM Thiébaud Weksteen wrote:
>
> The audit data currently captures which process and which target
> is responsible for a denial. There is no data on where exactly in the
> process that call occurred. Debugging can be made easier by being able to
> reconstruct the
Hi Maxime
On Wed, 8 Jul 2020 at 18:44, Maxime Ripard wrote:
>
> Now that the driver is ready for it, let's bring in the HDMI controllers
> variants for the BCM2711.
>
> Signed-off-by: Maxime Ripard
Reviewed-by: Dave Stevenson
> ---
> drivers/gpu/drm/vc4/vc4_hdmi.c | 278
Em Tue, Jul 28, 2020 at 03:01:00PM +0200, Jiri Olsa escreveu:
> On Tue, Jul 28, 2020 at 02:54:56PM +0200, Jiri Olsa wrote:
> > On Tue, Jul 28, 2020 at 09:39:55AM -0300, Arnaldo Carvalho de Melo wrote:
> > > Em Mon, Jul 20, 2020 at 09:16:25PM +0200, Jiri Olsa escreveu:
> > > > On Mon, Jul 20, 2020
On Tue, Jul 28, 2020 at 2:28 AM Sivaprakash Murugesan
wrote:
>
> On 7/28/2020 11:19 AM, Stephen Rothwell wrote:
> > Hi all,
> >
> > Today's linux-next merge of the devicetree tree got a conflict in:
> >
> >Documentation/devicetree/bindings/pci/qcom,pcie.txt
> >
> > between commits:
> >
> >
Hi Richard,
On 20-07-28 17:05, Richard Neumann wrote:
> Hi,
>
> Am Dienstag, den 28.07.2020, 16:58 +0200 schrieb Marco Felsch:
> > Hi,
> >
> > On 20-05-29 17:21, Andy Shevchenko wrote:
> > > On Fri, May 29, 2020 at 4:42 PM Sandeep Singh <
> > > sandeep.si...@amd.com> wrote:
> > > > From:
Hi Hans,
On 7/21/20 7:37 AM, Hans Verkuil wrote:
> On 17/07/2020 13:54, Helen Koike wrote:
>> From: Boris Brezillon
>>
>> This is part of the multiplanar and singleplanar unification process.
>> v4l2_ext_pix_format is supposed to work for both cases.
>>
>> We also add the concept of modifiers
Hi Paul,
在 2020/7/25 下午8:58, Paul Cercueil 写道:
Hi Zhou,
I'm a bit lost in all these JZ4770 PHY patchsets...
Anyway, the move from drivers/usb/phy to drivers/phy should be done
before adding anything else to the driver, so right after the
devicetree change. Here, your patch modifies things
Validate modes in the drm_crtc_helper_funcs.mode_valid() callback, which
is designed for this purpose, instead of doing it in
drm_crtc_helper_funcs.atomic_check().
Signed-off-by: Paul Cercueil
---
drivers/gpu/drm/ingenic/ingenic-drm-drv.c | 34 +--
1 file changed, 20
On Tue, Jul 28, 2020 at 08:56:41PM +0800, Muchun Song wrote:
On Mon, Jul 27, 2020 at 10:12 PM Greg Kroah-Hartman
wrote:
From: Muchun Song
commit d38a2b7a9c939e6d7329ab92b96559ccebf7b135 upstream.
If the kmem_cache refcount is greater than one, we should not mark the
root kmem_cache as
drm_atomic_get_plane_state() can return errors, so we need to handle
these.
Signed-off-by: Paul Cercueil
---
drivers/gpu/drm/ingenic/ingenic-drm-drv.c | 7 +++
1 file changed, 7 insertions(+)
diff --git a/drivers/gpu/drm/ingenic/ingenic-drm-drv.c
Here are a few cleanups to the ingenic-drm driver.
- some error paths were missing and have been added;
- the mode validation has been moved to the .mode_valid helper callback.
Cheers,
-Paul
Paul Cercueil (2):
drm/ingenic: Handle errors of drm_atomic_get_plane_state
drm/ingenic: Validate
From: madve...@linux.microsoft.com
> Sent: 28 July 2020 14:11
...
> The kernel creates the trampoline mapping without any permissions. When
> the trampoline is executed by user code, a page fault happens and the
> kernel gets control. The kernel recognizes that this is a trampoline
> invocation.
On Tue, 28 Jul 2020 at 13:30, Ingo Molnar wrote:
>
>
> * Marco Elver wrote:
>
> > To improve the general usefulness of the IRQ state trace information
> > with KCSAN enabled, save and restore the trace information when entering
> > and exiting the KCSAN runtime as well as when generating a KCSAN
From: Rafael J. Wysocki
Move the locking away from intel_pstate_set_energy_pref_index()
into its only caller and drop the (now redundant) return_pref label
from it.
Also move the "raw" EPP value check into the caller of that function,
so as to do it before acquiring the mutex, and reduce code
From: Rafael J. Wysocki
Allow intel_pstate to work in the passive mode with HWP enabled and
make it set the HWP minimum performance limit (HWP floor) to the
P-state value given by the target frequency supplied by the cpufreq
governor, so as to prevent the HWP algorithm and the CPU scheduler
from
Uses .probe_new in place of .probe. Also uses device_get_match_data()
for whoami matching.
Signed-off-by: Daniel Campello
---
drivers/iio/proximity/sx9310.c | 37 --
1 file changed, 13 insertions(+), 24 deletions(-)
diff --git a/drivers/iio/proximity/sx9310.c
Fixes enable/disable irq handling at various points. The driver needs to
only enable/disable irqs if there is an actual irq handler installed.
Signed-off-by: Daniel Campello
---
drivers/iio/proximity/sx9310.c | 24 +++-
1 file changed, 15 insertions(+), 9 deletions(-)
diff
Hi All,
On Monday, July 27, 2020 5:13:40 PM CEST Rafael J. Wysocki wrote:
>
> On Thursday, July 16, 2020 7:37:04 PM CEST Rafael J. Wysocki wrote:
> >
> > This really is a v2 of this patch:
> >
> > https://patchwork.kernel.org/patch/11663271/
> >
> > with an extra preceding cleanup patch to
Avoids unused warnings due to acpi/of table macros.
Signed-off-by: Daniel Campello
Reported-by: kbuild test robot
---
drivers/iio/proximity/sx9310.c | 5 ++---
1 file changed, 2 insertions(+), 3 deletions(-)
diff --git a/drivers/iio/proximity/sx9310.c b/drivers/iio/proximity/sx9310.c
index
Follows spec sheet for macro declarations.
Signed-off-by: Daniel Campello
---
drivers/iio/proximity/sx9310.c | 143 +++--
1 file changed, 67 insertions(+), 76 deletions(-)
diff --git a/drivers/iio/proximity/sx9310.c b/drivers/iio/proximity/sx9310.c
index
From: Stephen Boyd
Enable the main power supply (vdd) and digital IO power supply (svdd)
during probe so that the i2c communication and device works properly on
boards that aggressively power gate these supplies.
Reviewed-by: Douglas Anderson
Signed-off-by: Stephen Boyd
Signed-off-by: Daniel
Adds device tree bandings for sx9310 sensor.
Signed-off-by: Daniel Campello
Cc: Hartmut Knaack
Cc: Lars-Peter Clausen
Cc: Peter Meerwald-Stadler
Cc: Rob Herring
Reviewed-by: Douglas Anderson
[swb...@chromium.org: Add both regulators and make them optional]
Signed-off-by: Stephen Boyd
---
Use __aligned(8) to ensure that the timestamp is correctly aligned
when we call push_to_buffers
Signed-off-by: Daniel Campello
---
drivers/iio/proximity/sx9310.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/drivers/iio/proximity/sx9310.c
Uses for_each_set_bit() macro to loop over channel bitmaps.
Signed-off-by: Daniel Campello
---
drivers/iio/proximity/sx9310.c | 24 +---
1 file changed, 13 insertions(+), 11 deletions(-)
diff --git a/drivers/iio/proximity/sx9310.c b/drivers/iio/proximity/sx9310.c
index
From: Stephen Boyd
This struct member isn't used. Drop it.
Fixes: 72ad02b15d63 ("iio: Add SEMTECH SX9310/9311 sensor driver")
Signed-off-by: Stephen Boyd
Reviewed-by: Douglas Anderson
Reviewed-by: Daniel Campello
Signed-off-by: Daniel Campello
---
drivers/iio/proximity/sx9310.c | 1 -
1
From: Stephen Boyd
Printks in the kernel have newlines at the end. Add them to the few
printks in this driver.
Reviewed-by: Daniel Campello
Reviewed-by: Douglas Anderson
Fixes: 72ad02b15d63 ("iio: Add SEMTECH SX9310/9311 sensor driver")
Signed-off-by: Stephen Boyd
Signed-off-by: Daniel
Miscellaneous format fixes throughout the whole file.
Signed-off-by: Daniel Campello
---
drivers/iio/proximity/sx9310.c | 28 ++--
1 file changed, 10 insertions(+), 18 deletions(-)
diff --git a/drivers/iio/proximity/sx9310.c b/drivers/iio/proximity/sx9310.c
index
Fixes wrong copyright year.
Signed-off-by: Daniel Campello
---
drivers/iio/proximity/sx9310.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/drivers/iio/proximity/sx9310.c b/drivers/iio/proximity/sx9310.c
index 3956fd679c6db9..31234691a31abf 100644
---
Improves readability by storing >dev in a local variable.
Signed-off-by: Daniel Campello
---
drivers/iio/proximity/sx9310.c | 30 +++---
1 file changed, 15 insertions(+), 15 deletions(-)
diff --git a/drivers/iio/proximity/sx9310.c b/drivers/iio/proximity/sx9310.c
index
Simplify compensation stage by using regmap_read_poll_timeout().
Signed-off-by: Daniel Campello
---
drivers/iio/proximity/sx9310.c | 25 ++---
1 file changed, 10 insertions(+), 15 deletions(-)
diff --git a/drivers/iio/proximity/sx9310.c b/drivers/iio/proximity/sx9310.c
…
> +++ b/arch/arm/mach-zx/zx296702-pm-domain.c
> @@ -170,7 +170,6 @@ static int zx296702_pd_probe(struct platform_device *pdev)
>
> pcubase = devm_ioremap_resource(>dev, res);
> if (IS_ERR(pcubase)) {
> - dev_err(>dev, "ioremap fail.\n");
> return -EIO;
>
Checks for non-zero return values to signal error conditions.
Signed-off-by: Daniel Campello
---
drivers/iio/proximity/sx9310.c | 52 +-
1 file changed, 26 insertions(+), 26 deletions(-)
diff --git a/drivers/iio/proximity/sx9310.c
The first patch resends the DT binding for the driver that was merged in
v5.8-rc1 with a small change to update for proper regulators. The second
through the eleventh patch fixes several issues dropped from v8 to v9
when the initial patch was merged. The twelveth patch fixes a few
printks that are
On Tue, Jul 28, 2020 at 8:49 AM Thiébaud Weksteen wrote:
>
> Thanks for the review! I'll send a new revision of the patch with the
> %x formatter and using the TP_CONDITION macro.
>
> On adding further information to the trace event, I would prefer
> adding the strict minimum to be able to
On Tue, 28 Jul 2020 17:05:29 +0200
Marek Behún wrote:
> @@ -736,6 +777,16 @@ struct phy_driver {
> int (*set_loopback)(struct phy_device *dev, bool enable);
> int (*get_sqi)(struct phy_device *dev);
> int (*get_sqi_max)(struct phy_device *dev);
> +
> + /* PHY LED support */
Hi Vinod,
在 2020/7/27 下午5:53, Vinod Koul 写道:
On 25-07-20, 15:34, Zhou Yanjie wrote:
Hi Felipe,
在 2020/7/25 下午2:16, Felipe Balbi 写道:
Hi,
周琰杰 (Zhou Yanjie) writes:
Add support for probing the phy-jz4770 driver on the JZ4780 SoC,
the X1000 SoC and the X1830 SoC from Ingenic.
Tested-by: 周正
Hi Maxime
On Wed, 8 Jul 2020 at 18:44, Maxime Ripard wrote:
>
> In order to avoid pixels getting stuck in an unflushable FIFO, we need when
> we disable the HDMI controller to switch away from getting our pixels from
> the pixelvalve and instead use blank pixels, and switch back to the
>
Yes, but:
include/linux/compiler_attributes.h
This file is linux-specific and cannot be used with ACPICA.
Bob
-Original Message-
From: Joe Perches
Sent: Monday, July 27, 2020 7:22 PM
To: Gustavo A. R. Silva ; Moore, Robert
; Rafael J. Wysocki ; Gustavo A. R.
Silva
Cc: Kaneda, Erik
Em Tue, Jul 28, 2020 at 04:42:02PM +0200, Jiri Olsa escreveu:
> On Sun, Jul 26, 2020 at 09:08:14PM -0700, Thomas Hebb wrote:
> > commit c8c188679ccf ("tools build: Use the same CC for feature detection
> > and actual build") changed these assignments from unconditional (:=) to
> > conditional (?=)
Hi Maxime
On Wed, 8 Jul 2020 at 18:44, Maxime Ripard wrote:
>
> The VID_CTL setup is done in several places in the driver even though it's
> not really required. Let's simplify it a bit to do the configuration in one
> go.
>
> Signed-off-by: Maxime Ripard
Reviewed-by: Dave Stevenson
> ---
>
On Tue, Jul 28, 2020 at 6:53 AM Johannes Weiner wrote:
>
> Commit 8c8c383c04f6 ("mm: memcontrol: try harder to set a new
> memory.high") inadvertently removed a callback to recalculate the
> writeback cache size in light of a newly configured memory.high limit.
>
> Without letting the writeback
Hi Dhiraj,
On 28/07/2020 16:30, Dhiraj Sharma wrote:
> As per eudyptula challenge task 10 I had to fix coding styles. Thus I
> used checkpatch.pl script and fixed a chunk of warnings and few errors.
As both drivers/staging/media/usbvision/Kconfig and .../TODO say, this
driver is deprecated and
This patch adds support for controlling the LEDs connected to several
families of Marvell PHYs via the PHY HW LED trigger API. These families
are: 88E1112, 88E1121R, 88E1240, 88E1340S, 88E1510 and 88E1545. More can
be added.
This patch does not yet add support for compound LED modes. This could
Hi,
this is v4 of my RFC adding support for LEDs connected to Marvell PHYs.
Please note that if you want to test this, you still need to first apply
the patch adding the LED private triggers support from Pavel's tree.
Many PHYs support various HW control modes for LEDs connected directly
to them.
This adds code for registering such LEDs when described in device tree
and also adds a new private LED trigger called phydev-hw-mode. When
this trigger is enabled for a LED, the various HW control modes which
the PHY
Hi,
Am Dienstag, den 28.07.2020, 16:58 +0200 schrieb Marco Felsch:
> Hi,
>
> On 20-05-29 17:21, Andy Shevchenko wrote:
> > On Fri, May 29, 2020 at 4:42 PM Sandeep Singh <
> > sandeep.si...@amd.com> wrote:
> > > From: Sandeep Singh
> > >
> > > AMD SFH(Sensor Fusion Hub) is HID based driver.SFH
Hi Maxime
On Wed, 8 Jul 2020 at 18:44, Maxime Ripard wrote:
>
> In order to prevent some pixels getting stuck in an unflushable FIFO on
> bcm2711, we need to enable the HVS, the pixelvalve (the CRTC) and the HDMI
> controller (the encoder) in an intertwined way, and with tight delays.
>
>
Hi Greg,
Apparently the patchset has no more comments.
Could you take the patches to your tree? At least 1st and 2nd.
Regards
Andrzej
On 13.07.2020 16:43, Andrzej Hajda wrote:
> Hi All,
>
> Thanks for comments.
>
> Changes since v8:
> - fixed typo in function name,
> - removed cocci script
On Tue, Jul 28, 2020 at 6:53 AM Johannes Weiner wrote:
>
> When an outside process lowers one of the memory limits of a cgroup
> (or uses the force_empty knob in cgroup1), direct reclaim is performed
> in the context of the write(), in order to directly enforce the new
> limit and have it being
Hi,
On 27/07/20 06:32, Srikar Dronamraju wrote:
> Add percpu coregroup maps and masks to create coregroup domain.
> If a coregroup doesn't exist, the coregroup domain will be degenerated
> in favour of SMT/CACHE domain.
>
So there's at least one arm64 platform out there with the same "pairs of
Hi Maxime
On Wed, 8 Jul 2020 at 18:44, Maxime Ripard wrote:
>
> In order to avoid a pixel getting stuck in an unflushable FIFO, we need to
> recenter the FIFO every time we're doing a modeset and not only if we're
> connected to an HDMI monitor.
>
> Signed-off-by: Maxime Ripard
Reviewed-by:
This is the start of the stable review cycle for the 4.19.135 release.
There are 85 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 made by Thu, 30 Jul 2020 15:01:05 +.
Anything
Hi Maxime
On Wed, 8 Jul 2020 at 18:44, Maxime Ripard wrote:
>
> The current code has some logic, disabled by default, to dump the register
> setup in the HDMI controller.
>
> However, since we're going to split those functions in multiple, shorter,
> functions that only make sense where they are
Hi Maxime
On Wed, 8 Jul 2020 at 18:44, Maxime Ripard wrote:
>
> The HDMI driver was registering a single ALSA card so far with the name
> vc4-hdmi.
>
> Obviously, this is not going to work anymore when will have multiple HDMI
s/will/we
> controllers since we will end up trying to register two
On Tue, Jul 28, 2020 at 08:56:41PM +0800, Muchun Song wrote:
> On Mon, Jul 27, 2020 at 10:12 PM Greg Kroah-Hartman
> wrote:
> >
> > From: Muchun Song
> >
> > commit d38a2b7a9c939e6d7329ab92b96559ccebf7b135 upstream.
> >
> > If the kmem_cache refcount is greater than one, we should not mark the
>
Hi,
On 20-05-29 17:21, Andy Shevchenko wrote:
> On Fri, May 29, 2020 at 4:42 PM Sandeep Singh wrote:
> >
> > From: Sandeep Singh
> >
> > AMD SFH(Sensor Fusion Hub) is HID based driver.SFH FW
> > is part of MP2 processor (MP2 which is an ARM® Cortex-M4
> > core based co-processor to x86) and it
Thanks. See inline..
On 7/28/20 9:50 AM, Oleg Nesterov wrote:
> On 07/28, madve...@linux.microsoft.com wrote:
>> +bool is_trampfd_vma(struct vm_area_struct *vma)
>> +{
>> +struct file *file = vma->vm_file;
>> +
>> +if (!file)
>> +return false;
>> +return
Hi Maxime
On Wed, 8 Jul 2020 at 18:44, Maxime Ripard wrote:
>
> The HSM clock needs to be running at 101% the pixel clock of the HDMI
> controller, however it's shared between the two HDMI controllers, which
> means that if the resolutions are different between the two HDMI
> controllers, and
Hi Maxime
On Wed, 8 Jul 2020 at 18:44, Maxime Ripard wrote:
>
> The HSM clock needs to be setup at around 101% of the pixel rate. This
> was done previously by setting the clock rate to 163.7MHz at probe time and
> only check in mode_valid whether the mode pixel clock was under the pixel
> clock
On Tue, Jul 28, 2020 at 08:00:04PM +0530, Dhiraj Sharma wrote:
> As per eudyptula challenge task 10 I had to fix coding styles.
That is not needed in a changelog text.
> Thus I
> used checkpatch.pl script and fixed a chunk of warnings and few errors.
Neither is this, please be specific about
On Tue, Jul 28, 2020 at 08:00:04PM +0530, Dhiraj Sharma wrote:
> As per eudyptula challenge task 10 I had to fix coding styles. Thus I
> used checkpatch.pl script and fixed a chunk of warnings and few errors.
>
> Signed-off-by: Dhiraj Sharma
> ---
> .../staging/media/usbvision/usbvision-video.c
On Tue, Jul 28, 2020 at 4:20 AM Alex Shi wrote:
>
>
>
> 在 2020/7/28 上午7:34, Alexander Duyck 写道:
> >> @@ -1876,6 +1876,12 @@ static unsigned noinline_for_stack
> >> move_pages_to_lru(struct lruvec *lruvec,
> >> *
> >> list_add(>lru,)
> >>
> Add the missing platform_device_unregister() before return
> from amiga_init_devices() in the error handling case.
Will the tag “Fixes” become helpful for the commit message?
…
> +++ b/arch/m68k/amiga/platform.c
> @@ -188,8 +188,10 @@ static int __init amiga_init_devices(void)
>
On 7/28/20 4:57 AM, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20200727:
>
on i386:
CONFIG_USB_USBNET=y
# CONFIG_USB_NET_AX8817X is not set
CONFIG_USB_NET_AX88179_178A=y
CONFIG_USB_NET_CDCETHER=m
CONFIG_USB_NET_CDC_EEM=m
CONFIG_USB_NET_CDC_NCM=y
CONFIG_USB_NET_HUAWEI_CDC_NCM=m
On Tue, Jul 28, 2020 at 3:50 PM Martijn Coenen wrote:
> On Mon, Jul 27, 2020 at 2:04 PM Jann Horn wrote:
> > - task B opens /dev/binder once, creating binder_proc instance P3
> > - P3 calls P2 (via magic handle 0) with (void*)1 as argument (two-way
> >transaction)
> > - P2 receives the
On 07/28, madve...@linux.microsoft.com wrote:
>
> +bool is_trampfd_vma(struct vm_area_struct *vma)
> +{
> + struct file *file = vma->vm_file;
> +
> + if (!file)
> + return false;
> + return !strcmp(file->f_path.dentry->d_name.name, trampfd_name);
Hmm, this looks
Hi,
On Sun, Jul 26, 2020 at 2:44 AM Stanimir Varbanov
wrote:
>
> Hi Stephen,
>
> On 7/25/20 12:17 AM, Stephen Boyd wrote:
> > From: Stephen Boyd
> >
> > The busy loop in rpmh_rsc_send_data() is written with the assumption
> > that the udelay will be preempted by the tcs_tx_done() irq handler
Hi Maxime
On Wed, 8 Jul 2020 at 18:44, Maxime Ripard wrote:
>
> The mode_valid hook on the encoder uses a pointer to a drm_encoder called
> crtc, which is pretty confusing. Let's rename it to encoder to make it
> clear what it is.
>
> Signed-off-by: Maxime Ripard
Reviewed-by: Dave Stevenson
On Sun, Jul 26, 2020 at 09:08:14PM -0700, Thomas Hebb wrote:
> commit c8c188679ccf ("tools build: Use the same CC for feature detection
> and actual build") changed these assignments from unconditional (:=) to
> conditional (?=) so that they wouldn't clobber values from the
> environment. However,
On 7/27/20 8:12 PM, Cong Wang wrote:
> On Mon, Jul 27, 2020 at 7:14 PM Gaurav Singh wrote:
>>
>> Add return to fix build issue. Haven't reproduced this issue at
>> my end.
>>
>> My hypothesis is this: In function: ip6_xmit(), we have
>> const struct ipv6_pinfo *np = inet6_sk(sk); which returns
On 7/28/20 3:42 AM, Crystal Guo wrote:
> mt8xxx-resets.h actually just used to define TOPRGU_SW_RST_NUM.
> Instead of resubmit the mt8xxx-reset.h for a new IC, get the number
> of reset bits from dtsi is more easier to maintain.
> > Signed-off-by: Crystal Guo
> ---
> drivers/watchdog/mtk_wdt.c |
Hi,
I have recently come across an RCU trace with the 5.8-rc7 kernel that has the
debug configs enabled while installing a VM on a CPU that is listed under
nohz_full.
Based on some of the initial debugging, my impression is that the issue is
triggered because of the fastpath that is meant to
Test the newly introduced KVM_MEM_PCI_HOLE memslots:
- Reads from all pages return '0xff'
- Writes to all pages cause KVM_EXIT_MMIO
Signed-off-by: Vitaly Kuznetsov
---
tools/testing/selftests/kvm/Makefile | 1 +
.../testing/selftests/kvm/include/kvm_util.h | 1 +
No functional change intended. Slot flags will need to be analyzed
prior to try_async_pf() when KVM_MEM_PCI_HOLE is implemented.
Signed-off-by: Vitaly Kuznetsov
---
arch/x86/kvm/mmu/mmu.c | 14 --
arch/x86/kvm/mmu/paging_tmpl.h | 7 +--
2 files changed, 13
This is a continuation of "[PATCH RFC 0/5] KVM: x86: KVM_MEM_ALLONES
memory" work:
https://lore.kernel.org/kvm/20200514180540.52407-1-vkuzn...@redhat.com/
and pairs with Julia's "x86/PCI: Use MMCONFIG by default for KVM guests":
PCIe config space can (depending on the configuration) be quite big but
usually is sparsely populated. Guest may scan it by accessing individual
device's page which, when device is missing, is supposed to have 'pci
hole' semantics: reads return '0xff' and writes get discarded. Compared
to the
[AMD Public Use]
> -Original Message-
> From: Kai-Heng Feng
> Sent: Tuesday, July 28, 2020 6:46 AM
> To: bhelg...@google.com
> Cc: Kai-Heng Feng ; Deucher, Alexander
> ; open list:PCI SUBSYSTEM p...@vger.kernel.org>; open list
> Subject: [PATCH] PCI: Mark AMD Navi10 GPU rev 0x00 ATS as
On Tue, 28 Jul 2020 at 18:33, Muchun Song wrote:
>
> Thanks for your test. I have reviewed the patch:
>
> [PATCH 4.19 76/86] mm: memcg/slab: fix memory leak at non-root
> kmem_cache destroy
>
> There is a backport problem and I have pointed out the problem in that email.
Thanks for your
One crash issue happened when directly down the network interface,
which nbd device is connected to. The kernel version is kernel
4.14.0-115.
According to the debug log and call trace, the buffer of ext4
superblock already unmapped after the network of nbd device down.
But the code continue to run
On 7/27/20 11:42 PM, Anson Huang wrote:
> According to reference manual, the i.MX7ULP WDOG's operations should
> follow below sequence:
>
> 1. disable global interrupts;
> 2. unlock the wdog and wait unlock bit set;
> 3. reconfigure the wdog and wait for reconfiguration bit set;
> 4. enabel
No I didn't intent to. I have sent another version.
Thank you very much, Dan.
Juan Antonio Aldea-Armenteros
On 7/28/2020 10:23 AM, Andy Lutomirski wrote:
>> On Jul 27, 2020, at 10:02 AM, Anthony Yznaga
>> wrote:
>>
>> This patchset adds support for preserving an anonymous memory range across
>> exec(3) using a new madvise MADV_DOEXEC argument. The primary benefit for
>> sharing memory in this
On 20-07-28 16:05, Matthias Schiffer wrote:
> On Tue, 2020-07-28 at 15:51 +0200, Marco Felsch wrote:
> > Hi Matthias,
> >
> > thanks for the patch.
> >
> > On 20-07-28 13:28, Matthias Schiffer wrote:
> > > In preparation for an update of the TQ-Systems TQMa7x/MBa7x DTS,
> > > add the
> > > QSPI
As per eudyptula challenge task 10 I had to fix coding styles. Thus I
used checkpatch.pl script and fixed a chunk of warnings and few errors.
Signed-off-by: Dhiraj Sharma
---
.../staging/media/usbvision/usbvision-video.c | 91 +++
1 file changed, 52 insertions(+), 39
Qinglang Miao 于2020年7月28日周二 上午10:24写道：
>
> There is a error message within devm_ioremap_resource
> already, so remove the dev_err call to avoid redundant
> error message.
>
> Signed-off-by: Qinglang Miao
> ---
> arch/arm/mach-zx/zx296702-pm-domain.c | 1 -
> 1 file changed, 1 deletion(-)
>
On Wed, 2020-07-22 at 12:11 +0300, Maxim Levitsky wrote:
> On Tue, 2020-07-21 at 22:55 -0400, Martin K. Petersen wrote:
> > Christoph,
> >
> > > Hmm, I wonder if we should simply add the check and warning to
> > > blk_queue_logical_block_size and add an error in that case. Then
> > > drivers
On Tue, Jul 28, 2020 at 04:00:46PM +0200, Dafna Hirschfeld wrote:
>
>
> On 28.07.20 14:07, Dafna Hirschfeld wrote:
> > Hi
> >
> > On 28.07.20 13:39, Kaaira Gupta wrote:
> > > On Mon, Jul 27, 2020 at 02:54:30PM -0300, Helen Koike wrote:
> > > > Hi,
> > > >
> > > > On 7/27/20 11:31 AM, Kieran
701 - 800 of 1424 matches
Mail list logo
