Probe the rpmsg_ctrl driver on virtio rpmsg bus creation.
This provides the possibility to expose an ioctrl to create
RPMsg channels.
Signed-off-by: Arnaud Pouliquen
---
drivers/rpmsg/virtio_rpmsg_bus.c | 36 +++-
1 file changed, 35 insertions(+), 1 deletion(-)
diff
On 31/07/20 12:27, Marc Zyngier wrote:
>> Look for anything that performs an interrupt allocation by calling
>> into the parent with a 3 cell (DT case) fwspec. There is a bunch
>> of them.
>
> For what it is worth, I have just pushed out a branch[1] containing some
> of this rework as well as
Implement the ioctrl function that parses the list of
rpmsg drivers registered to create an associated device.
Signed-off-by: Arnaud Pouliquen
---
drivers/rpmsg/rpmsg_ctrl.c | 39 --
1 file changed, 37 insertions(+), 2 deletions(-)
diff --git
The override field is already used in the rpmsg_device.
This allows to force a service name to be associated to
a RPMsg service driver.
Adding this field in the channel info allows to force the channel
creation with a specified RPMsg service driver.
Signed-off-by: Arnaud Pouliquen
---
Add API for RPMsg driver to register the supported service.
This API has to be called during RPMsg driver init to declare the
service. Then the RPMsg control will be able to instantiate
associated device.
Signed-off-by: Arnaud Pouliquen
---
drivers/rpmsg/rpmsg_ctrl.c | 57
This function creates the rpmsg_ctl device using the
driver_override to link device to the driver.
Signed-off-by: Arnaud Pouliquen
---
drivers/rpmsg/rpmsg_internal.h | 15 +++
1 file changed, 15 insertions(+)
diff --git a/drivers/rpmsg/rpmsg_internal.h
Add the support of the release of an endpoint using the ioctl
interface.
The endpoint is identified using its name, its source address
and is destination address.
To support legacy a new ioctl ioctl is created instead of updating
RPMSG_DESTROY_EPT_IOCTL.
Signed-off-by: Arnaud Pouliquen
---
Add new structure for RPMsg driver registration.
This structure will be used to link a service to its driver.
Signed-off-by: Arnaud Pouliquen
---
include/linux/rpmsg.h | 13 +
1 file changed, 13 insertions(+)
diff --git a/include/linux/rpmsg.h b/include/linux/rpmsg.h
index
Use the override information from the channel info structure
to set the rpdev override and so link the channel to a specific
driver.
Signed-off-by: Arnaud Pouliquen
---
drivers/rpmsg/virtio_rpmsg_bus.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/rpmsg/virtio_rpmsg_bus.c
To allow to associate an endpoint creation to a service, add
a new parameter in rpmsg_endpoint_info struct.
For each RPMsg service driver that want to support the ioctl interface
a new service will have to be added.
The RPMSG_START_PRIVATE_SERVICES is used to allow developer to add is
own
Create a RPMsg driver that will offer to the userspace applications an
ioctl to manage channels.
As a first step, this driver just creates the /dev/rpmsg_ctl
( is the instance value). The ioctl is not implemented.
Notice that this driver is associated to a RPMsg device with no endpoint.
This serie is inspired by the RPMsg char driver. The RPMsg char driver
provides interfaces that:
- expose a char RPMsg device for communication with the remote processor
- expose controls interface for applications to create and release channels
The purpose of this series is to decorrelate the
On 31.07.20 03:08, Martin KaFai Lau wrote:
> On Thu, Jul 30, 2020 at 04:07:14PM +0200, KP Singh wrote:
>> From: KP Singh
>>
>> Similar to bpf_local_storage for sockets, add local storage for inodes.
>> The life-cycle of storage is managed with the life-cycle of the inode.
>> i.e. the storage
31.07.2020 12:02, Sowjanya Komatineni пишет:
> This patch separates implementation of CSI stream enable and disable
> into separate functions for readability.
>
> Signed-off-by: Sowjanya Komatineni
> ---
> drivers/staging/media/tegra-video/csi.c | 51
> ++---
> 1
If there is only a single NUMA node in the system, the only NUMA topology
level that will be generated will be NODE (identity distance), which
doesn't have SD_SERIALIZE.
This means we don't need this special case in sd_parent_degenerate(), as
having the NODE level "naturally" covers it. Thus,
Commit b73287f0b074 ("ASoC: soc-pcm: dpcm: fix playback/capture checks")
changed the meaning of dpcm_playback/dpcm_capture and now requires the
CPU DAI BE to aligned with those flags.
This broke all Amlogic cards with uni-directional backends (All gx and
most axg cards).
While I'm still confused
To associate the SD flags with some metadata, we need some more structure
in the way they are declared.
Rather than shove that in a free-standing macro list, move the declaration
in a separate file that can be re-imported with different SD_FLAG
definitions. This is inspired by what is done with
We currently set this flag *only* on domains whose topology level exactly
match the level where we detect asymmetry (as returned by
asym_cpu_capacity_level()). This is rather problematic.
Say there are two clusters in the system, one with a lone big CPU and the
other with a mix of big and LITTLE
Now that we have some description of what we expect the flags layout to
be, we can use that to assert at runtime that the actual layout is sane.
Signed-off-by: Valentin Schneider
---
kernel/sched/topology.c | 17 +
1 file changed, 17 insertions(+)
diff --git
Leverage SD_DEGENERATE_GROUPS_MASK in sd_degenerate() and
sd_parent_degenerate(). The negation of SD_DEGENERATE_GROUPS_MASK is used
as the mask of flags not requiring groups, which is equivalent to
SD_WAKE_AFFINE, IOW is the same as what we have now.
Suggested-by: Peter Zijlstra
Signed-off-by:
In preparation of cleaning up the sd_degenerate*() functions, mark flags
that are only relevant when their associated domain has more than a single
group. With this, build a compile-time mask of those SD flags.
Suggested-by: Peter Zijlstra
Signed-off-by: Valentin Schneider
---
> On 31 Jul 2020, at 13:59, Greg Kroah-Hartman
> wrote:
>
> On Fri, Jul 31, 2020 at 01:14:09PM +0200, Håkon Bugge wrote:
>>
>>
>>> On 31 Jul 2020, at 11:59, Dan Carpenter wrote:
>>>
>>> On Fri, Jul 31, 2020 at 07:53:01AM +0300, Leon Romanovsky wrote:
On Thu, Jul 30, 2020 at
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
removed, at which point ARM no longer benefits from having a custom defined
topology
There are some expectations regarding how sched domain flags should be laid
out, but none of them are checked or asserted in
sched_domain_debug_one(). After staring at said flags for a while, I've
come to realize they all (except *one*) fall in either of two categories:
- Shared with children:
I don't think it is going to change much in practice, but we were missing
those:
o SD_BALANCE_WAKE: Used just like the other SD_BALANCE_* flags, so also
needs > 1 group.
o SD_ASYM_PACKING: Hinges on load balancing (periodic / wakeup), thus needs
> 1 group to happen
o SD_OVERLAP: Describes
Hi,
I've repeatedly stared at an SD flag and asked myself "how should that be
set up in the domain hierarchy anyway?". I figured that if we formalize our
flags zoology a bit, we could also do some runtime assertions on them -
this is what this series is all about.
Patches
===
The idea is to
This flag was introduced in 2014 by commit
d77b3ed5c9f8 ("sched: Add a new SD_SHARE_POWERDOMAIN for sched_domain")
but AFAIA it was never leveraged by the scheduler. The closest thing I can
think of is EAS caring about frequency domains, and it does that by
leveraging performance domains.
Em Thu, Jul 30, 2020 at 05:28:43PM -0400, Steven Rostedt escreveu:
>
> Arnaldo,
>
> Can you pull this into your tree under urgent?
>
>
> https://lore.kernel.org/linux-trace-devel/20200730150236.5392-1-pduples...@efficios.com/
>
> Reviewed-by: Steven Rostedt (VMware)
Sure, will get it and
On failure pcie_capability_read_word() sets it's last parameter, val
to 0. In which case (val & PCI_EXP_DEVCTL2_LTR_EN) evaluates to 0.
However, with Patch 12/12, it is possible that val is set to ~0 on
failure. This would introduce a bug because (x & x) == (~0 & x).
Since ~0 is an invalid value
On failure pcie_capability_read_word() sets it's last parameter, val
to 0. However, with Patch 12/12, it is possible that val is set to
~0 on failure. This introduces a bug because (x & x) == (~0 & x).
Since ~0 is an invalid value here,
pciehp_get_power_status():
Add an extra check for ~0 on the
On failure pcie_capability_read_dword() sets it's last parameter,
val to 0. In this case dn and up will be 0, so aspm_hw_l1_supported()
will return false.
However, with Patch 12/12, it is possible that val is set to ~0 on
failure. This would introduce a bug because (x & x) == (~0 & x). So
with dn
The default case of the switch statement is redundant since
PCI_EXP_SLTCTL_PCC is only a single bit.
Set the default case in the switch-statement to set status
to "Power On"
Suggested-by: Bjorn Helgaas
Signed-off-by: Saheed O. Bolarinwa
---
drivers/pci/hotplug/pciehp_hpc.c | 6 ++
1 file
On failure pcie_capability_read_dword() sets it's last parameter, val
to 0. However, with Patch 12/12, it is possible that val is set to ~0
on failure. This would introduce a bug because (x & x) == (~0 & x).
Since ~0 is an invalid value here,
Add an extra check for ~0 to the if condition to
On failure pcie_capability_read_*() sets it's last parameter, val
to 0. However, with Patch 12/12, it is possible that val is set
to ~0 on failure. This would introduces a bug because
(x & x) == (~0 & x).
Since ~0 is an invalid value in here,
Add extra check for ~0 in the if condition to ensure
On failure pcie_capability_read_dword() sets it's last parameter, val
to 0. However, with Patch 12/12, it is possible that val is set to ~0
on failure. This would introduce a bug because (x & x) == (~0 & x).
Since ~0 is an invalid value here,
Add an extra check for ~0 to the if condition to
v4 CHANGES:
- Drop uses of pcie_capability_read_*() return value. This related to
[1] which is pointing towards making the accessors return void.
- Remove patches found to be unnecessary
- Reword some commit messages
v3 CHANGES:
- Split previous PATCH 6/13 into two : PATCH 6/14 and PATCH 7/14
-
OLED display consist of an OLED panel and a display controller.
The displays that were used on yapp4 platform were based on a SSD1305
controller. These displays are now discontinued and we need to add
support for a replacement.
The new display is based on SSD1309 controller and requires slightly
Add devicetree binding for Orion - new board variant in the Y Soft
IOTA family.
Signed-off-by: Michal Vokáč
---
Documentation/devicetree/bindings/arm/fsl.yaml | 1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation/devicetree/bindings/arm/fsl.yaml
Add devicetree for new variant of the Y Soft IOT appliance.
The board is based on Hydra with the following changes:
- faster SoC (1GHz), 4GB RAM and 64GB eMMC
- removed miniPCIe
- removed Audio jack
- removed uSD slot
- removed RJ10 serial
- HDMI replaced by USB host
Signed-off-by: Michal
On Thu, 30 Jul 2020 at 13:38, Greg Kroah-Hartman
wrote:
>
> This is the start of the stable review cycle for the 4.19.136 release.
> There are 17 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.
>
>
On 30.07.20 10:59, Vitaly Kuznetsov wrote:
Alexander Graf writes:
It's not desireable to have all MSRs always handled by KVM kernel space. Some
MSRs would be useful to handle in user space to either emulate behavior (like
uCode updates) or differentiate whether they are valid based on the
在 2020/7/30 18:03, Arnaldo Carvalho de Melo 写道:
Em Wed, Jul 29, 2020 at 04:47:36PM -0700, Ian Rogers escreveu:
On Fri, Jul 24, 2020 at 3:07 AM Wang ShaoBo wrote:
Function jvmti_write_code called by compiled_method_load_cb may return
error in using fwrite_unlocked, this failure should be
On Fri, Jul 31, 2020 at 01:14:09PM +0200, Håkon Bugge wrote:
>
>
> > On 31 Jul 2020, at 11:59, Dan Carpenter wrote:
> >
> > On Fri, Jul 31, 2020 at 07:53:01AM +0300, Leon Romanovsky wrote:
> >> On Thu, Jul 30, 2020 at 03:20:26PM -0400, Peilin Ye wrote:
> >>> rds_notify_queue_get() is
On Thu, 30 Jul 2020 13:44:14 +0200,
Hillf Danton wrote:
>
>
> Wed, 29 Jul 2020 22:53:21 -0700
> > syzbot found the following issue on:
> >
> > HEAD commit:d3590ebf Merge tag 'audit-pr-20200729' of git://git.kernel..
> > git tree: upstream
> > console output:
On Wed, 29 Jul 2020 at 20:43, David Lechner wrote:
>
> On 7/28/20 4:18 AM, Grzegorz Jaszczyk wrote:
> > The Programmable Real-Time Unit Subsystem (PRUSS) contains a local
> > interrupt controller (INTC) that can handle various system input events
> > and post interrupts back to the device-level
On Fri, 2020-07-31 at 16:25 +0800, Yanhu Cao wrote:
> When doing some tests with multiple mds, there are many
> mds forwarding requests between them and then the client request
> is resent.
>
> If the request is a modification operation and the mode is set to
> USE_AUTH_MDS.
> Auth mds should be
On Thu, Jul 30, 2020 at 09:35:15AM +0200, Ilya Leoshkevich wrote:
> On Thu, 2020-07-30 at 14:36 +0800, Wang Hai wrote:
> > test_unwind() misses to call kfree(bt) in an error path.
> > Add the missed function call to fix it.
> >
> > Fixes: 0610154650f1 ("s390/test_unwind: print verbose unwinding
>
On Wed, 29 Jul 2020 at 19:34, David Lechner wrote:
>
> On 7/28/20 4:18 AM, Grzegorz Jaszczyk wrote:
> > From: Suman Anna
> >
> > The Programmable Real-Time Unit and Industrial Communication Subsystem
> > (PRU-ICSS or simply PRUSS) contains an interrupt controller (INTC) that
> > can handle
On Fri, Jul 31, 2020 at 12:32 PM Naresh Kamboju
wrote:
>
> On Thu, 30 Jul 2020 at 13:36, Greg Kroah-Hartman
> wrote:
> >
> > This is the start of the stable review cycle for the 5.4.55 release.
> > There are 19 patches in this series, all will be posted as a response
> > to this one. If anyone
The name service announcement should not be linked to the RPMsg virtio bus
but to the RPMsg protocol itself.
This patch proposes to break the dependency with the RPmsg virtio bus by
the introduction of the reserved RPMsg name service driver which will be in
charge of managing the RPMsg name
Add the channel creation API as a first step to be able to define the
name service announcement as a rpmsg driver independent from the RPMsg
virtio bus.
Signed-off-by: Arnaud Pouliquen
---
drivers/rpmsg/rpmsg_core.c | 37 ++
drivers/rpmsg/rpmsg_internal.h |
Rename the internal function as it is internal, and as
the name will be used in rpmsg_core.
Signed-off-by: Arnaud Pouliquen
---
drivers/rpmsg/virtio_rpmsg_bus.c | 7 ---
1 file changed, 4 insertions(+), 3 deletions(-)
diff --git a/drivers/rpmsg/virtio_rpmsg_bus.c
As generic NS driver is available, rely on it for NS management instead of
managing it in RPMsg virtio bus.
Signed-off-by: Arnaud Pouliquen
---
drivers/rpmsg/Kconfig| 1 +
drivers/rpmsg/virtio_rpmsg_bus.c | 86
2 files changed, 21 insertions(+), 66
Use the new rpmsg_ns API to send the name service announcements if
the VIRTIO_RPMSG_F_NS is set, else just not implement the ops.
Signed-off-by: Arnaud Pouliquen
---
drivers/rpmsg/virtio_rpmsg_bus.c | 94 +---
1 file changed, 13 insertions(+), 81 deletions(-)
diff
As the RPMsg driver is in charge of the name service announcement,
create an API to send channel creation and destruction to the remote
processor.
Notice that the source address of the message sent is now RPMSG_NS_ADDR.
Legacy implementation was to send the message with source address
The NS announcement is implemented by several backends, but could be
considered as part the RPMsg protocol.
In this case it should be managed as a reserved rpmsg service and so
implemented on top of the rpmsg protocol.
This series introduces the rpmsg_ns driver that handles the name service
Implement the create and release of the RPMsg channel
for the RPMsg virtio bus.
Signed-off-by: Arnaud Pouliquen
---
drivers/rpmsg/virtio_rpmsg_bus.c | 27 +++
1 file changed, 27 insertions(+)
diff --git a/drivers/rpmsg/virtio_rpmsg_bus.c
The endianness has to be fixed to ensure that both sides can
decode the message. The Little endian format is used according
to the generic virtio implementation.
Signed-off-by: Arnaud Pouliquen
---
drivers/rpmsg/rpmsg_ns.c | 17 +
1 file changed, 9 insertions(+), 8 deletions(-)
The address 53 is reserved for the dynamic RPMsg device management
on name service announcement.
Define this address in a reserved enum list.
Signed-off-by: Arnaud Pouliquen
---
drivers/rpmsg/virtio_rpmsg_bus.c | 3 ---
include/linux/rpmsg.h| 9 +
2 files changed, 9
Function jvmti_write_code called by compiled_method_load_cb may return
error in using fwrite_unlocked, this failure should be captured and
warned.
Signed-off-by: Wang ShaoBo
---
tools/perf/jvmti/jvmti_agent.c | 25 -
1 file changed, 16 insertions(+), 9 deletions(-)
diff
On 31.07.20 05:20, Jim Mattson wrote:
CAUTION: This email originated from outside of the organization. Do not click
links or open attachments unless you can confirm the sender and know the
content is safe.
On Thu, Jul 30, 2020 at 4:53 PM Jim Mattson wrote:
On Thu, Jul 30, 2020 at 4:08
31.07.2020 12:02, Sowjanya Komatineni пишет:
...
> @@ -249,13 +249,47 @@ static int tegra_csi_enable_stream(struct v4l2_subdev
> *subdev)
> return ret;
> }
>
> + if (csi_chan->mipi) {
> + ret = tegra_mipi_enable(csi_chan->mipi);
> + if (ret < 0) {
On Fri, Jul 31, 2020 at 5:39 AM Neal Liu wrote:
>
> Fixing CFI issue which introduced by commit efe9711214e6 is
> incomplete.
> Add return value to fix return-type build warning.
>
> Signed-off-by: Neal Liu
Applied with edited subject and changelog, but ->
> ---
>
On 07/29/2020 10:01 PM, Mathieu Poirier wrote:
On Wed, Jul 22, 2020 at 06:20:29PM +0100, Suzuki K Poulose wrote:
TPIU driver access the device before the coresight device
is registered. In other words, before the drvdata->csdev
is valid. Thus, we need to make sure that the csdev_access
is valid
Srikar Dronamraju writes:
> * Michael Ellerman [2020-07-31 17:49:55]:
>
>> Srikar Dronamraju writes:
>> > Add support for grouping cores based on the device-tree classification.
>> > - The last domain in the associativity domains always refers to the
>> > core.
>> > - If primary reference
Srikar Dronamraju writes:
> * Michael Ellerman [2020-07-31 18:02:21]:
>
>> Srikar Dronamraju writes:
>> > Lookup the coregroup id from the associativity array.
>
> Thanks Michael for all your comments and inputs.
>
>> It's slightly strange that this is called in patch 9, but only properly
>>
Fix trivia typo Not -> Note in the comment to DO_ONCE().
Signed-off-by: Andy Shevchenko
---
include/linux/once.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/include/linux/once.h b/include/linux/once.h
index 9225ee6d96c7..095c6debd63b 100644
--- a/include/linux/once.h
+++
Dear Linux people,
we have a backup server with two xfs filesystems on 101.9TB md-raid6 devices
(16 * 7.3 T disks) each, Current Linux version is 5.4.54.
The server is doing lot of metadata i/o to these filesystems (two rsync of
complete client filesystems with --link-dest to the previous
On 2020-07-31 09:08, Marc Zyngier wrote:
Hi Valentin,
On 2020-07-31 01:08, Valentin Schneider wrote:
Hi Marc,
On 30/07/20 19:10, Marc Zyngier wrote:
[...]
diff --git a/drivers/irqchip/irq-gic.c b/drivers/irqchip/irq-gic.c
index e2b4cae88bce..a91ce1e73bd2 100644
---
Hi Hsin-Yi,
Thank you for your patch.
On 27/7/20 9:41, Hsin-Yi Wang wrote:
> bus-width and non-removable is not used by the driver.
> max-frequency should be spi-max-frequency for flash node.
>
> Fixes: 689b937bedde ("arm64: dts: mediatek: add mt8173 elm and hana board")
> Reported-by: Nicolas
Hi all,
Changes since 20200730:
My fixes tree contains:
dbf24e30ce2e ("device_cgroup: Fix RCU list debugging warning")
Linus' tree lost its build failure but gained another for which I applied
a patch.
The block/zonefs trees gained a conflict against Linus' tree.
I reverted 4 commits from
On Fri, Jul 31, 2020 at 2:44 AM Agrawal, Akshu wrote:
>
>
> On 7/29/2020 6:56 AM, Stephen Boyd wrote:
> > Quoting Akshu Agrawal (2020-07-28 01:28:53)
> >> AMD SoC general pupose clk is present in new platforms with
> >> same MMIO mappings. We can reuse the same clk handler support
> >> for other
> On 31 Jul 2020, at 11:59, Dan Carpenter wrote:
>
> On Fri, Jul 31, 2020 at 07:53:01AM +0300, Leon Romanovsky wrote:
>> On Thu, Jul 30, 2020 at 03:20:26PM -0400, Peilin Ye wrote:
>>> rds_notify_queue_get() is potentially copying uninitialized kernel stack
>>> memory to userspace since the
On Fri, 31 Jul 2020, Gene Chen wrote:
> Lee Jones 於 2020年7月28日 週二 下午2:54寫道：
> >
> > On Tue, 28 Jul 2020, Gene Chen wrote:
> >
> > > Lee Jones 於 2020年7月27日 週一 下午7:29寫道：
> > > >
> > > > On Fri, 17 Jul 2020, Gene Chen wrote:
> > > >
> > > > > From: Gene Chen
> > > > >
> > > > > Combine mt6360
Thanks Peter, this looks like a great start.
> Perhaps the two of you could work together to come up with a common
tracepoint that addresses both needs.
Agreed.
> 1 Filtering. Types goes to trace so we can put up a filter for contexts or
> type etc.
That's right. I think this is the main
Lee Jones 於 2020年7月28日 週二 下午2:54寫道：
>
> On Tue, 28 Jul 2020, Gene Chen wrote:
>
> > Lee Jones 於 2020年7月27日 週一 下午7:29寫道：
> > >
> > > On Fri, 17 Jul 2020, Gene Chen wrote:
> > >
> > > > From: Gene Chen
> > > >
> > > > Combine mt6360 pmic/ldo resouces into mt6360 regulator resources
> > > > to
> congrats to version 1.0.4 and hope to see it in the Debian repositories soon.
>
Thanks Sven!
root# dpkg -l | grep exfatprogs | awk '/^ii/ {print $1 " " $2 " " $3}'
| column -t
ii exfatprogs 1.0.4-1
- Sedat -
Hi Andy,
thanks for further review. If nobody else sends comments, I'll
publish the next version tonight. Maybe we could clarify the questions
below in time.
Best regards
Christian
> W=1 (not V=1) runs kernel doc validation script.
without V=1, I get nothing. Neither excess nor missing members
The parameter 'priority' is incorrectly forced to zero which ultimately
induces logically dead code in the subsequent lines.
Fixes: 57ba4c9b56d8 ("fsl/fman: Add FMan MAC support")
Signed-off-by: Florinel Iordache
---
drivers/net/ethernet/freescale/fman/fman_memac.c | 1 -
1 file changed, 1
Check before using returned value to avoid dereferencing null pointer.
Fixes: 18a6c85fcc78 ("fsl/fman: Add FMan Port Support")
Signed-off-by: Florinel Iordache
---
drivers/net/ethernet/freescale/fman/fman_port.c | 9 -
1 file changed, 8 insertions(+), 1 deletion(-)
diff --git
Fix memory allocation for ethernet address hash table.
The code was wrongly allocating an array for eth hash table which
is incorrect because this is the main structure for eth hash table
(struct eth_hash_t) that contains inside a number of elements.
Fixes: 57ba4c9b56d8 ("fsl/fman: Add FMan MAC
Add a safe check to avoid dereferencing null pointer
Fixes: 57ba4c9b56d8 ("fsl/fman: Add FMan MAC support")
Signed-off-by: Florinel Iordache
---
drivers/net/ethernet/freescale/fman/fman_dtsec.c | 4 ++--
drivers/net/ethernet/freescale/fman/fman_memac.c | 2 +-
Potentially overflowing expression (ts_freq << 16 and intgr << 16)
declared as type u32 (32-bit unsigned) is evaluated using 32-bit
arithmetic and then used in a context that expects an expression of
type u64 (64-bit unsigned) which ultimately is used as 16-bit
unsigned by typecasting to u16.
Here are several fixes for the DPAA FMan driver.
v2 changes:
* corrected patch 4 by removing the line added by mistake
* used longer fixes tags with the first 12 characters of the SHA-1 ID
Florinel Iordache (5):
fsl/fman: use 32-bit unsigned integer
fsl/fman: fix dereference null return
Check that alloc and free types of functions match each other.
Signed-off-by: Denis Efremov
---
Changes in v2:
- Lines are limited to 80 characters where possible
- Confidence changed from High to Medium because of
fs/btrfs/send.c:1119 false-positive
- __vmalloc_area_node() explicitly
> Please let me know if you need further help.
>
> - Arnaldo
Hi Arnaldo,
YES, I need further help.
I have published in [1] numbers for "perf stat make ..." with
GNU/gcc+binutils vs. LLVM toolchain for building Linux v5.8-rc7.
[ GNU/gcc+binutils toolchain ]
10964.876434769 seconds time
Add initial dts support for Xiaomi Poco F1 (Beryllium).
This initial support is based on upstream Dragonboard 845c
(sdm845) device. With this dts, Beryllium boots AOSP up to
ADB shell over USB-C.
Supported functionality includes UFS, USB-C (peripheral),
microSD card and Vol+/Vol-/power keys.
On 31.07.20 11:18, David Hildenbrand wrote:
Grml, forgot to add cc: list for this patch, ccing the right people.
> virtio-mem adds memory in memory block granularity, to be able to
> remove it in the same granularity again later, and to grow slowly on
> demand. This, however, results in quite a
Hi Shengjiu,
On Fri, Jul 31, 2020 at 3:32 AM Shengjiu Wang wrote:
>
> The fifo_depth is 64 on i.MX8QM/i.MX8QXP, 128 on i.MX8MQ, 16 on
> i.MX7ULP.
>
> Original FSL_SAI_CR1_RFW_MASK value 0x1F is not suitable for
> these platform, the FIFO watermark mask should be updated
> according to the
在 2020/7/31 下午12:24, Florian Fainelli 写道:
Disable pref 30 by utilizing the standard quirk method and matching the
affected SoCs: 7344, 7346, 7425.
Signed-off-by: Florian Fainelli
---
arch/mips/bmips/setup.c | 17 +
1 file changed, 17 insertions(+)
diff --git
On Thu, 30 Jul 2020 at 13:36, Greg Kroah-Hartman
wrote:
>
> This is the start of the stable review cycle for the 5.4.55 release.
> There are 19 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.
>
>
Hi!
I've just got the following WARNING followed by a BUG on rc7. Maybe it's
already a known issue, but here it is anyway.
Cheers,
--
Luis
[ 38.001304] [ cut here ]
[ 38.001312] list_add corruption. prev->next should be next
(8fe713397b88), but was
On 2020/07/31 18:41, h...@infradead.org wrote:
> On Fri, Jul 31, 2020 at 09:34:50AM +, Damien Le Moal wrote:
>> Sync writes are done under the inode lock, so there cannot be other writers
>> at
>> the same time. And for the sync case, since the actual written offset is
>> necessarily equal to
On Thu, Jul 30, 2020 at 08:15:12PM +, Pincus, Josh wrote:
> We were looking into a similar enhancement for the Virt I/O MMIO transport
> and came across this project.
> This enhancement would be perfect for us.
>
> Has there been any progress since Feb, 2020? It looks like the effort might
Hi Nathan,
On Thu, 2020-07-30 at 18:10 -0700, Nathan Chancellor wrote:
> On Tue, Jul 28, 2020 at 12:09:18PM +0200, Christoph Hellwig wrote:
> > Ok, I found a slight bug that wasn't intended. I wanted to make sure
> > we can always fall back to a lower pool, but got that wrong. Should be
> >
On 31/07/20 11:20 am, Brendan Higgins wrote:
> On Thu, Jul 30, 2020 at 5:18 AM Arpitha Raghunandan <98.a...@gmail.com> wrote:
>>
>> Converts test lib/test_uuid.c to KUnit
>
> Can you add some more detail to the commit message? Maybe link to
> KUnit and say something about why this change is
Hi Ingo,
On Fri, 31 Jul 2020 11:57:35 +0200 Ingo Molnar wrote:
>
> I've merged Linus's latest into tip:locking/core, keeping the simpler
> solution of a6342915881a and reducing the dependency hell.
>
> Will push it all out hopefully later today (unrelated changes need
> more testing), from
bus->count_cells() parses cells starting from the node's parent. This is
not good enough for parser_init() which is generally parsing a bus node.
Revert to previous behavior using of_bus_n_*_cells().
Fixes: 2f96593ecc37 ("of_address: Add bus type match for pci ranges parser")
Reported-by: Nathan
On 31.07.2020 01:01, Jonathan Bakker wrote:
> The parallel port nodes should be numbered 1 and 2, not 0 and 1
> for A and B respectively. The driver has always implemented 1
> and 2 and the in-tree Goni DTS uses 1 as port A as well. Update
> the documentation to match this behaviour.
>
>
On Fri, Jul 31, 2020 at 07:53:01AM +0300, Leon Romanovsky wrote:
> On Thu, Jul 30, 2020 at 03:20:26PM -0400, Peilin Ye wrote:
> > rds_notify_queue_get() is potentially copying uninitialized kernel stack
> > memory to userspace since the compiler may leave a 4-byte hole at the end
> > of `cmsg`.
>
701 - 800 of 1159 matches
Mail list logo
