Hi Bjorn,
> On Nov 30, 2020, at 4:25 PM, Bjorn Helgaas wrote:
>
> On Mon, Nov 30, 2020 at 07:54:37PM +, Kelley, Sean V wrote:
>>> On Nov 24, 2020, at 9:17 AM, Bjorn Helgaas wrote:
>>> On Mon, Nov 23, 2020 at 11:57:35PM +, Kelley, Sean V wrote:
> On Nov 23, 2020, at 3:28 PM, Bjorn
Hi all,
Commit
03d99e5d63da ("nvme-fcloop: add sysfs attribute to inject command drop")
is missing a Signed-off-by from its committer.
--
Cheers,
Stephen Rothwell
pgpRJjlkkexNk.pgp
Description: OpenPGP digital signature
The pull request you sent on Wed, 2 Dec 2020 06:51:47 -0500:
> https://git.kernel.org/pub/scm/linux/kernel/git/mst/vhost.git tags/for_linus
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/2c6ffa9e9b11bdfa267fe05ad1e98d3491b4224f
Thank you!
--
Deet-doot-dot, I am a
The pull request you sent on Tue, 1 Dec 2020 20:22:39 -0500:
> git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace.git
> trace-v5.10-rc6-bootconfig
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/8a02ec8f35779335b81577903832c2b3c495e979
Thank you!
--
The pull request you sent on Wed, 02 Dec 2020 10:07:14 +0100:
> git://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound.git
> tags/sound-5.10-rc7
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/bb95d60783f1ac85883c7ae33cafa85236b6179e
Thank you!
--
Deet-doot-dot,
From: Rafał Miłecki
BCM4908 SoCs have USB 2.0 PHY and USB 3.0 PHY attached to the MDIO bus.
Those bindings allow describing them.
Signed-off-by: Rafał Miłecki
---
.../bindings/phy/bcm4908-usb-phy.yaml | 52 +++
1 file changed, 52 insertions(+)
create mode 100644
On Wed, Dec 02, 2020 at 09:22:36PM +0100, David Hildenbrand wrote:
> On 02.12.20 20:26, Minchan Kim wrote:
> > On Wed, Dec 02, 2020 at 07:51:07PM +0100, Michal Hocko wrote:
> >> On Wed 02-12-20 09:54:29, Minchan Kim wrote:
> >>> On Wed, Dec 02, 2020 at 05:48:34PM +0100, Michal Hocko wrote:
>
The pull request you sent on Wed, 2 Dec 2020 17:17:51 +:
> git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git tags/arm64-fixes
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/3bb61aa61828499a7d0f5e560051625fd02ae7e4
Thank you!
--
Deet-doot-dot, I am a
From: Rafał Miłecki
This driver initializes BCM4908 USB PHYs so USB can be utilized.
Signed-off-by: Rafał Miłecki
---
drivers/phy/broadcom/Kconfig | 9 ++
drivers/phy/broadcom/Makefile | 1 +
drivers/phy/broadcom/phy-bcm4908-usb.c | 204 +
3
On Wed, 02 Dec 2020, Jarkko Sakkinen wrote:
On Wed, Dec 02, 2020 at 12:58:05PM +0200, Adrian Ratiu wrote:
From: "dlau...@chromium.org" Add TPM
2.0 compatible I2C interface for chips with cr50 firmware.
The firmware running on the currently supported H1 MCU requires
a special driver to
Convert internals of protocol implementation to use protocol handles and
expose a new protocol operations interface for SCMI driver using the new
get/put common operations, while keeping the old handle->power_ops still
around to ease transition.
Remove handle->power_priv now unused.
Port driver to the new SCMI Sensor interface based on protocol handles
and common devm_get_ops().
Signed-off-by: Cristian Marussi
---
drivers/hwmon/scmi-hwmon.c | 24 +++-
1 file changed, 15 insertions(+), 9 deletions(-)
diff --git a/drivers/hwmon/scmi-hwmon.c
Now that all the SCMI driver users have been migrated to the new interface
remove the legacy interface and all the transient code.
Signed-off-by: Cristian Marussi
---
drivers/firmware/arm_scmi/clock.c | 67 ---
include/linux/scmi_protocol.h | 15 ---
2 files
Notification private data is currently accessible via handle->notify_priv;
this data was indeed meant to be private to the notification core support
and not to be accessible by SCMI drivers: make it private hiding it inside
instance descriptor struct scmi_info and accessible only via dedicated
On Tue, Dec 1, 2020 at 6:16 PM Ira Weiny wrote:
>
> This will force a change to xfstests at a minimum. And I do know of users who
> have been using this value. But I have gotten inquires about using the
> feature
> so there are users out there.
If it's only a few tests that fail, I wouldn't
Convert internals of protocol implementation to use protocol handles and
expose a new protocol operations interface for SCMI driver using the new
get/put common operations, while keeping the old handle->voltage_ops still
around to ease transition.
Remove handle->voltage_priv now unused.
Port driver to the new SCMI Voltage interface based on protocol handles
and common devm_get_ops().
Signed-off-by: Cristian Marussi
---
drivers/regulator/scmi-regulator.c | 39 --
1 file changed, 21 insertions(+), 18 deletions(-)
diff --git
Now that all the protocol private variable data have been moved out of
struct scmi_handle, mark all of its references as const.
Signed-off-by: Cristian Marussi
---
drivers/firmware/arm_scmi/common.h | 4 ++--
drivers/firmware/arm_scmi/driver.c | 12 ++--
include/linux/scmi_protocol.h
Remove all the events registration code used to ease the transition to the
new interface based on protocol handles..
Signed-off-by: Cristian Marussi
---
drivers/firmware/arm_scmi/base.c| 4 ++--
drivers/firmware/arm_scmi/notify.h | 6 +++---
drivers/firmware/arm_scmi/perf.c| 9
Convert internals of protocol implementation to use protocol handles and
expose a new protocol operations interface for SCMI driver using the new
get/put common operations, while keeping the old handle->sensor_ops still
around to ease transition.
Remove handle->sensor_priv now unused.
Port driver to the new SCMI Clock interface based on protocol handles
and common devm_get_ops().
Signed-off-by: Cristian Marussi
---
drivers/clk/clk-scmi.c | 27 +--
1 file changed, 17 insertions(+), 10 deletions(-)
diff --git a/drivers/clk/clk-scmi.c
Now that all the SCMI driver users have been migrated to the new interface
remove the legacy interface and all the transient code.
Signed-off-by: Cristian Marussi
---
drivers/firmware/arm_scmi/sensors.c | 82 -
include/linux/scmi_protocol.h | 19 ---
2
Convert internals of protocol implementation to use protocol handles and
expose a new protocol operations interface for SCMI driver using the new
get/put common operations, while keeping the old handle->clk_ops still
around to ease transition.
Remove handle->clock_priv now unused.
Signed-off-by:
Having added the support for SCMI protocols as modules in order to let
vendors extend the SCMI core with their own additions it seems odd to
then force SCMI drivers built on top to use a static device table to
declare their devices since this way any new SCMI drivers addition
would need the core
Port driver to the new SCMI Power interface based on protocol handles
and common devm_get_ops().
Signed-off-by: Cristian Marussi
---
drivers/firmware/arm_scmi/scmi_pm_domain.c | 26 +-
1 file changed, 16 insertions(+), 10 deletions(-)
diff --git
Now that all the SCMI driver users have been migrated to the new interface
remove the legacy interface and all the transient code.
Signed-off-by: Cristian Marussi
---
drivers/firmware/arm_scmi/voltage.c | 67 -
include/linux/scmi_protocol.h | 16 ---
2
Extend SCMI protocols accounting mechanism to address possible module
usage and add the support to possibly define new protocols as loadable
modules.
Keep Standard protocols built into the SCMI core.
Signed-off-by: Cristian Marussi
---
drivers/firmware/arm_scmi/base.c| 2 ++
Remove unused core scmi_xfer wrappers now that we have migrated all
protocols to the new interface based on protocol handles.
Signed-off-by: Cristian Marussi
---
drivers/firmware/arm_scmi/common.h | 15 -
drivers/firmware/arm_scmi/driver.c | 91 --
2 files
Now that all protocols and drivers have been ported to the new interface
based on protocol handles and get/put operations, remove all the legacy
transient initialization code.
Signed-off-by: Cristian Marussi
---
drivers/firmware/arm_scmi/bus.c| 26 +-
Convert internals of protocol implementation to use protocol handles and
expose a new protocol operations interface for SCMI driver using the new
get/put common operations.
Remove handle->system_priv now unused.
Signed-off-by: Cristian Marussi
---
drivers/firmware/arm_scmi/system.c | 30
Now that all the SCMI driver users have been migrated to the new interface
remove the legacy interface and all the transient code.
Signed-off-by: Cristian Marussi
---
drivers/firmware/arm_scmi/reset.c | 68 ---
include/linux/scmi_protocol.h | 11 -
2 files
Port driver to the new SCMI Reset interface based on protocol handles
and common devm_get_ops().
Signed-off-by: Cristian Marussi
---
drivers/reset/reset-scmi.c | 33 -
1 file changed, 20 insertions(+), 13 deletions(-)
diff --git a/drivers/reset/reset-scmi.c
Convert internals of protocol implementation to use protocol handles and
expose a new protocol operations interface for SCMI driver using the new
get/put common operations, while keeping the old handle->reset_ops still
around to ease transition.
Remove handle->reset_priv now unused.
Now that all the SCMI driver users have been migrated to the new interface
remove the legacy interface and all the transient code.
Signed-off-by: Cristian Marussi
---
drivers/firmware/arm_scmi/perf.c | 111 ---
include/linux/scmi_protocol.h| 26
2 files
Now that all the SCMI driver users have been migrated to the new interface
remove the legacy interface and all the transient code.
Signed-off-by: Cristian Marussi
---
drivers/firmware/arm_scmi/power.c | 47 ---
include/linux/scmi_protocol.h | 11
2 files
Add new core SCMI xfer operations based on protocol handles to enable
protocols to builds and send their own protocol specific messages.
Keep old original scmi_xfer_ operations interface as wrappers around the
new interface in order to let coexist old and new interfaces to ease
protocol by
Convert internals of protocol implementation to use protocol handles and
expose a new protocol operations interface for SCMI driver using the new
get/put common operations, while keeping the old handle->perf_ops still
around to ease transition.
Remove handle->perf_priv now unused.
Signed-off-by:
Port Base protocol to new protocol handles based interface.
Signed-off-by: Cristian Marussi
---
drivers/firmware/arm_scmi/base.c | 117 +++--
drivers/firmware/arm_scmi/common.h | 3 +-
drivers/firmware/arm_scmi/driver.c | 14 +++-
3 files changed, 71 insertions(+),
Port driver to the new SCMI Perf interface based on protocol handles
and common devm_get_ops().
Signed-off-by: Cristian Marussi
---
drivers/cpufreq/scmi-cpufreq.c | 35 ++
1 file changed, 19 insertions(+), 16 deletions(-)
diff --git
Convert refactored events registration routines to use protocol handles.
In order to maintain bisectability and to allow protocols and drivers
to be later ported to the new protocol handle interface one by one,
introduce here also some transient code and typing that will be removed
later in order
Account for any active registered notifier against the proper related
protocol; do not consider pending event handlers, only active handlers
will concur to protocol usage accounting.
Signed-off-by: Cristian Marussi
---
drivers/firmware/arm_scmi/notify.c | 51 ++
1
Add an helper to grab, from a protocol handle, the handle common memory
area allocated to store SCMI version data which is exposed on sysfs.
Such helper will be needed by SCMI Base protocol initialization once it
will be moved to new protocol handles scheme.
Signed-off-by: Cristian Marussi
---
Add a new refactored protocol events registration helper and invoke it
from the centralized initialization process triggered by get_ops() and
friends.
Add a .get_num_sources as a new optional callback amongst protocol events
operations; finally remove events registration call-sites from within
Expose to the SCMI drivers a new alternative devres managed notifications
API based on protocol handles.
All drivers still keep using the old API, no functional change.
Signed-off-by: Cristian Marussi
---
drivers/firmware/arm_scmi/notify.c | 123 +
On Wed, Dec 02, 2020 at 08:06:01PM +0100, Greg Kroah-Hartman wrote:
> On Wed, Dec 02, 2020 at 06:41:43PM +0100, Miklos Szeredi wrote:
> > On Wed, Dec 2, 2020 at 5:24 PM David Howells wrote:
> > >
> > > Miklos Szeredi wrote:
> > >
> > > > Stable cc also?
> > > >
> > > > Cc: # 5.8
> > >
> > >
Add basic protocol handles definitions and private data helpers support.
A protocol handle identifies a protocol instance initialized against a
specific handle; it embeds all the references to the core SCMI xfer methods
that will be needed by a protocol implementation to build and send its own
Expose to the SCMI drivers a non managed version of a common protocols API
based on generic get/put methods and protocol handles.
All drivers still keep using the old API, no functional change.
Signed-off-by: Cristian Marussi
---
These non devres methods are probably not needed, given the devm_
Expose to the SCMI drivers a new devres managed common protocols API based
on generic get/put methods and protocol handles.
All drivers still keep using the old API, no functional change.
Signed-off-by: Cristian Marussi
---
drivers/firmware/arm_scmi/driver.c | 92 ++
Extend common protocol registration routines and provide some new generic
protocols get/put helpers that can track protocols usage and automatically
perform the proper initialization and de-initialization on demand when
required.
Convert all standard protocols to use this new registration scheme
Hi all,
The current SCMI implementation does not provide an interface to easily
develop and include a custom vendor protocol implementation as prescribed
by the SCMI standard, also because, there is not currently any custom
protocol in the upstream to justify the development of a custom interface
Good day,
On Wed, Dec 02, 2020 at 12:05:55PM +0100, Guennadi Liakhovetski wrote:
> Hi Mathieu,
>
> I'd like to resume reviewing and begin upstreaming of the next steps of
> my Audio DSP Virtualisation work, based on this your patch set. How
I'm all for it too.
> confident are we that it's
, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch]
url:
https://github.com/0day-ci/linux/commits/Gene-Chen/leds-mt6360-Add-LED-driver-for-MT6360/20201202-185224
base: git://git.kernel.org/pub/scm/linux/kernel/git/pavel/linux-leds.git
for-next
config
On Wed, 2020-12-02 at 20:12 +, Joao Martins wrote:
> > I'll do some more experiments and
> > see what I can get working, and what it looks like.
> >
> > I'm focusing on making the shinfo stuff all use kvm_map_gfn() first.
> >
>
> I was chatting with Ankur, and we can't fully 100% remember
On Thu, 2020-12-03 at 01:52 +0530, Dwaipayan Ray wrote:
> Commit log lines starting with a '#' can be dropped by git if
> the corresponding commit message is reworded by a maintainer.
> This minor error can be easily avoided if checkpatch warns
> for the same.
This makes no sense to me.
How
Hi, Dear maintainers,
> A bus lock [1] is acquired through either split locked access to writeback
> (WB)
> memory or any locked access to non-WB memory. This is typically >1000
> cycles slower than an atomic operation within a cache line. It also disrupts
> performance on other cores.
...
>
On Mon, Nov 30, 2020 at 08:59:49AM +0530, Anshuman Khandual wrote:
> This series adds a mechanism allowing platforms to weigh in and prevalidate
> incoming address range before proceeding further with the memory hotplug.
> This helps prevent potential platform errors for the given address range,
>
On 2020-12-02 2:44 a.m., Joao Martins wrote:
[late response - was on holiday yesterday]
On 12/2/20 12:40 AM, Ankur Arora wrote:
On 2020-12-01 5:07 a.m., David Woodhouse wrote:
On Wed, 2019-02-20 at 20:15 +, Joao Martins wrote:
+static int kvm_xen_shared_info_init(struct kvm *kvm, gfn_t
On Mon, Nov 30, 2020 at 08:59:52AM +0530, Anshuman Khandual wrote:
> This overrides arch_get_mappabble_range() on s390 platform and drops now
> redundant similar check in vmem_add_mapping(). This compensates by adding
> a new check __segment_load() to preserve the existing functionality.
>
> Cc:
On Sun, Nov 29, 2020 at 10:37:18AM +0800, Baolin Wang wrote:
> The ioc_refreash_vrate() will only be called in ioc_timer_fn() after
> starting a new period or stopping the period.
>
> So when starting a new period, the variable 'pleft' in ioc_refreash_vrate()
> is always the period's time, which
On Wed, Nov 11, 2020 at 05:55:27AM -0800, syzbot wrote:
> Hello,
>
> syzbot found the following issue on:
>
> HEAD commit:407ab579 Merge tag 'for-linus' of git://git.kernel.org/pub..
> git tree: upstream
> console output: https://syzkaller.appspot.com/x/log.txt?x=16d8406250
>
On 2020-12-02 4:20 a.m., David Woodhouse wrote:
On Wed, 2020-12-02 at 10:44 +, Joao Martins wrote:
[late response - was on holiday yesterday]
On 12/2/20 12:40 AM, Ankur Arora wrote:
On 2020-12-01 5:07 a.m., David Woodhouse wrote:
On Wed, 2019-02-20 at 20:15 +, Joao Martins wrote:
On Tue, 2020-12-01 at 16:55 -0800, Andrii Nakryiko wrote:
> On Fri, Nov 27, 2020 at 8:09 AM Yonghong Song wrote:
> >
> >
> > On 11/27/20 3:20 AM, KP Singh wrote:
> > > On Fri, Nov 27, 2020 at 8:35 AM Yonghong Song wrote:
> > > >
> > > > In this case, module name may be truncated and user did
Two clock divider tables are missing sentinel at the end. Effect of that
is that clock framework reads past the last entry. Fix that with adding
sentinel at the end.
Issue was discovered with KASan.
Fixes: 0577e4853bfb ("clk: sunxi-ng: Add H3 clocks")
Fixes: c6a0637460c2 ("clk: sunxi-ng: Add A64
From: Nick Terrell
Adds decompress_sources.h which includes every .c file necessary for
zstd decompression. This is used in decompress_unzstd.c so the internal
structure of the library isn't exposed.
This allows us to upgrade the zstd library version without modifying any
callers. Instead we
From: Nick Terrell
Please pull from
g...@github.com:terrelln/linux.git tags/zstd-1.4.6-v6
to get these changes. Alternatively the patchset is included.
This patchset upgrades the zstd library to the latest upstream release. The
current zstd version in the kernel is a modified version of
On 02.12.20 20:26, Minchan Kim wrote:
> On Wed, Dec 02, 2020 at 07:51:07PM +0100, Michal Hocko wrote:
>> On Wed 02-12-20 09:54:29, Minchan Kim wrote:
>>> On Wed, Dec 02, 2020 at 05:48:34PM +0100, Michal Hocko wrote:
On Wed 02-12-20 08:15:49, Minchan Kim wrote:
> On Wed, Dec 02, 2020 at
From: Bean Huo
The CMD13 polling is only needed for the command with R1B Resp. For the
command with R1 Resp, such as open-ended multiple block read/write
(CMD18/25) commands, the device will just wait for its next paired command.
There is no need to poll device status through CMD13.
Meanwhile,
Commit log lines starting with a '#' can be dropped by git if
the corresponding commit message is reworded by a maintainer.
This minor error can be easily avoided if checkpatch warns
for the same.
Add a new check which emits a warning on finding lines starting
with a '#'. Also add a quick fix by
On Wed, Dec 02, 2020 at 05:21:58AM +, Surendrakumar Upadhyay, TejaskumarX
wrote:
> Yes it fails all the tests which are allocating from this stolen
> memory bunch. For example IGT tests like "
> igt@kms_frontbuffer_tracking@-[fbc|fbcpsr].* |
> igt@kms_fbcon_fbt@fbc.* " are failing as they
On Fri, Nov 27, 2020 at 01:30:21PM +0800, Shengjiu Wang wrote:
> The driver is initially designed for sound card using HDMI
> interface on i.MX platform. There is internal HDMI IP or
> external HDMI modules connect with SAI or AUD2HTX interface.
> It supports both transmitter and receiver devices.
> With Doug's recent fixes in the DMA handling and the introduction of
> proper iommu configuration, which Caleb tested [1], I think we're good
> without this on the OnePlus. Caleb, please confirm.
Yes, he confirmed already. I missed it was private only.
Thanks for your heads up, too!
Hello, Neil.
(cc'ing Lai)
On Fri, Nov 20, 2020 at 10:07:56AM +1100, NeilBrown wrote:
> If the workqueue maintainers are unmovable in the position that a
> CM-workitem must not use excessive CPU ever, and so must not call
> cond_resched(), then I can take that back to the NFS maintainers and
Oh,
On Wed, Dec 02, 2020 at 05:18:12PM +0800, Chiqijun wrote:
> On 2020/11/30 23:46, Alex Williamson wrote:
> > On Sat, 28 Nov 2020 17:29:19 -0600
> > Bjorn Helgaas wrote:
> > > On Sat, Nov 28, 2020 at 02:18:25PM +0800, Chiqijun wrote:
> > > > When multiple VFs do FLR at the same time, the firmware
Jarod Wilson wrote:
>On Wed, Dec 2, 2020 at 12:55 PM Jay Vosburgh
>wrote:
>>
>> Jarod Wilson wrote:
>>
>> >Don't try to adjust XFRM support flags if the bond device isn't yet
>> >registered. Bad things can currently happen when netdev_change_features()
>> >is called without having
On Wed, Dec 2, 2020 at 4:54 AM Masahiro Yamada wrote:
>
> Just a nit:
> Now that the test code does not include any header,
> you can also delete
> "-I $srctree/gcc-plugins -I $gccplugins_dir/include"
Ahh,m yes.
It sounds like we might be able to delete the build test entirely if
we just always
On 12/2/20 7:02 PM, David Woodhouse wrote:
> On Wed, 2020-12-02 at 18:34 +, Joao Martins wrote:
>> On 12/2/20 4:47 PM, David Woodhouse wrote:
>>> On Wed, 2020-12-02 at 13:12 +, Joao Martins wrote:
On 12/2/20 11:17 AM, David Woodhouse wrote:
>>> For the VMM
>>> API I think we should
s/s0ix/S0ix/ in subject.
On Wed, Dec 02, 2020 at 10:17:47AM -0600, Mario Limonciello wrote:
> These comet lake systems are not yet released, but have been validated
> on pre-release hardware.
s/comet lake/Comet Lake/ to match previous usage in patch 3/5.
> This is being submitted separately
On Thu, 2020-12-03 at 01:30 +0530, Dwaipayan Ray wrote:
> On Wed, Dec 2, 2020 at 3:45 PM Dwaipayan Ray wrote:
> >
> > Commit log lines starting with a '#' can be dropped by git if
> > the corresponding commit message is reworded by a maintainer.
> > This minor error can be easily avoided if
s/it's/its/ (in subject as well as below).
Previous patches used "S0ix", not "s0ix" (in subject as well as
below, as well as subject and commit log of 3/5 and 5/5).
On Wed, Dec 02, 2020 at 10:17:45AM -0600, Mario Limonciello wrote:
> Introduce a flag to indicate the device should be using the
On Wed, Dec 02, 2020 at 10:17:44AM -0600, Mario Limonciello wrote:
> From: Vitaly Lifshits
>
> Changed a configuration in the flows to align with
> architecture requirements to achieve S0i3.2 substate.
I guess this is really talking about requirements of a specific
CPU/SOC before it will enter
The following commit has been merged into the x86/platform branch of tip:
Commit-ID: fa4a379ecfa0c735e8979bb732fe5a1705a64052
Gitweb:
https://git.kernel.org/tip/fa4a379ecfa0c735e8979bb732fe5a1705a64052
Author:Dan Carpenter
AuthorDate:Wed, 02 Dec 2020 17:44:07 +03:00
Hello dear,
We are sending this message to all the people that have been
scammed in every part of the world, the UN agreed upon to
compensate them with the sum of US$500,000 (Five hundred thousand
United State Dollars Only).
This includes every foreign contractors that may have not
It was <2020-12-02 śro 09:18>, when Jakub Kicinski wrote:
> On Wed, 02 Dec 2020 11:46:28 +0100 Lukasz Stelmach wrote:
>> >> + status = netif_rx(skb);
>> >
>> > If I'm reading things right this is in process context, so netif_rx_ni()
>> >
>>
>> Is it? The stack looks as follows
>>
>>
On Tue, Nov 17, 2020 at 09:11:06PM +0100, Krzysztof Kozlowski wrote:
> The SMDK6410 DTS was incorrectly called mini6410, probably copy-paste
> from FriendlyARM Mini6410 board.
>
> Signed-off-by: Krzysztof Kozlowski
> ---
> arch/arm/boot/dts/s3c6410-smdk6410.dts | 2 +-
> 1 file changed, 1
On Tue, Nov 17, 2020 at 09:11:04PM +0100, Krzysztof Kozlowski wrote:
> Add bindings for the FriendlyARM Mini6410 and Samsung SMDK6410 boards.
>
> Signed-off-by: Krzysztof Kozlowski
> ---
> .../devicetree/bindings/arm/samsung/samsung-boards.yaml| 7 +++
> 1 file changed, 7 insertions(+)
On Wed, 2 Dec 2020, Vitaly Wool wrote:
> On Wed, Dec 2, 2020 at 7:06 PM Nicolas Pitre wrote:
> >
> > On Wed, 2 Dec 2020, Vitaly Wool wrote:
> >
> > > Introduce XIP (eXecute In Place) support for RISC-V platforms.
> > > It allows code to be executed directly from non-volatile storage
> > >
On Tue, Nov 17, 2020 at 09:11:05PM +0100, Krzysztof Kozlowski wrote:
> Add a compatible for SMDK2416 board next to the SoC compatible.
>
> Signed-off-by: Krzysztof Kozlowski
> ---
> arch/arm/boot/dts/s3c2416-smdk2416.dts | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
Applied.
Best
Add gpio-line-names as documented on gitbooks [1] and in the
schematics [2].
[1]: https://bananapi.gitbook.io/bpi-m2/en/bpi-m2_gpio_pin_define
[2]: https://drive.google.com/file/d/0B4PAo2nW2KfnRERWNnJGSGxJbmM/view
Signed-off-by: Michael Klein
---
.../boot/dts/sun6i-a31s-sinovoip-bpi-m2.dts |
This DT property can be 0, 16, and then 64, but not 32. The math here
doesn't recognize this slight bump in the power of 2 numbers and
translates a DT property of 64 into the register value '3' when it
really should be '2'. Fix it by subtracting one more if the number being
translated is larger
On Tue, Nov 17, 2020 at 09:11:03PM +0100, Krzysztof Kozlowski wrote:
> Add binding for the SMDK2416 board.
>
> Signed-off-by: Krzysztof Kozlowski
> ---
> .../devicetree/bindings/arm/samsung/samsung-boards.yaml | 6 ++
> 1 file changed, 6 insertions(+)
Applied.
Best regards,
Krzysztof
On Wed, 2 Dec 2020 12:33:00 +0530 Sunil Kovvuri wrote:
> On Wed, Dec 2, 2020 at 12:28 PM Dan Carpenter
> wrote:
> > These debugfs never return NULL so all this code will never be run.
> >
> > In the normal case, (and in this case particularly), the debugfs
> > functions are not supposed to be
On Wed, Dec 02, 2020 at 11:25:46AM -0800, Kees Cook wrote:
> On Wed, Dec 02, 2020 at 09:45:31AM +0300, Dan Carpenter wrote:
> > The crypto_alloc_comp() function never returns NULL, it returns error
> > pointers on error.
> >
> > Signed-off-by: Dan Carpenter
>
> I replied to an identical patch
On Wed, Dec 2, 2020 at 3:45 PM Dwaipayan Ray wrote:
>
> Commit log lines starting with a '#' can be dropped by git if
> the corresponding commit message is reworded by a maintainer.
> This minor error can be easily avoided if checkpatch warns
> for the same.
>
> Add a new check which emits a
Bring some order to the list of SoCs. No functional change.
Signed-off-by: Krzysztof Kozlowski
---
drivers/soc/samsung/exynos-chipid.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/drivers/soc/samsung/exynos-chipid.c
b/drivers/soc/samsung/exynos-chipid.c
index
The Exynos ChipID driver on Exynos SoCs has only informational
purpose - to expose the SoC device in sysfs. No other drivers
depend on it so there is really no benefit of initializing it early.
Instead, initialize everything with arch_initcall which:
1. Allows to use dev_info() as the SoC bus is
Hi Miquel,
On 2/12/20 9:31 pm, Miquel Raynal wrote:
> Hi Chris,
>
> Chris Packham wrote on Wed, 2 Dec
> 2020 08:23:13 +:
>
>> Hi Miquel,
>>
>> On 2/12/20 8:59 pm, Miquel Raynal wrote:
>>> Hi Chris,
>>>
>>> Chris Packham wrote on Wed, 2 Dec
>>> 2020 07:47:32 +:
>>>
Hi,
On Thu, Nov 26, 2020 at 04:16:15PM +0800, Baolin Wang wrote:
> Factor out the base vrate change code into a separate function
> to fimplify the ioc_timer_fn().
>
> No functional change.
>
> Signed-off-by: Baolin Wang
Acked-by: Tejun Heo
Thanks.
--
tejun
On Tue, 1 Dec 2020 12:39:09 +0100 Schrempf Frieder wrote:
> From: Frieder Schrempf
>
> There are other NXP NCI compatible NFC controllers such as the PN7150
> that use an integrated firmware and therefore do not have a GPIO to
> select firmware downloading mode. To support this kind of
On Thu, Nov 26, 2020 at 04:16:14PM +0800, Baolin Wang wrote:
> Factor out the iocgs' state check into a separate function to
> simplify the ioc_timer_fn().
>
> No functional change.
>
> Signed-off-by: Baolin Wang
Acked-by: Tejun Heo
Thanks.
--
tejun
On Thu, Nov 26, 2020 at 04:16:13PM +0800, Baolin Wang wrote:
> We only use the hweight based usage ratio to calculate the new
> hweight_inuse of the iocg to decide if this iocg can donate some
> surplus vtime.
>
> Thus move the usage ratio calculation to the correct place to
> avoid unnecessary
501 - 600 of 1675 matches
Mail list logo
