The RTL838x/839x family of SoCs are Realtek switches with an embedded
MIPS core.
* RTL838x - 500MHz 4kce single core - 1Gbit ports and L2 features
* RTL839x - 700MHz 34Kc single core - 1Gbit ports and L2 features
These switches, depending on the exact part number, will have anywhere
between 8
On Wed, 30 Dec 2020, Arnd Bergmann wrote:
> From: Arnd Bergmann
>
> clang warns because the added __maybe_unused attribute is in
> the wrong place:
>
> drivers/i3c/master/mipi-i3c-hci/core.c:780:21: error: attribute declaration
> must precede definition [-Werror,-Wignored-attributes]
> static
This is just enough system to boot the kernel with earlycon working.
Signed-off-by: Bert Vermeulen
Signed-off-by: Sander Vanheule
---
arch/mips/Kconfig | 21 ++
arch/mips/generic/Platform | 1 +
arch/mips/include/asm/realtek/ioremap.h | 29
Signed-off-by: Bert Vermeulen
Signed-off-by: Sander Vanheule
---
Documentation/devicetree/bindings/vendor-prefixes.yaml | 2 ++
1 file changed, 2 insertions(+)
diff --git a/Documentation/devicetree/bindings/vendor-prefixes.yaml
b/Documentation/devicetree/bindings/vendor-prefixes.yaml
index
Signed-off-by: Bert Vermeulen
Signed-off-by: Sander Vanheule
---
arch/mips/Kconfig | 10 +++
arch/mips/boot/dts/realtek/Makefile | 2 +
arch/mips/boot/dts/realtek/cisco_sg220-26.dts | 81 +++
3 files changed, 93 insertions(+)
create mode
Hi Pavel,
Thank you for the patch.
On Wed, Dec 30, 2020 at 01:55:50PM +0100, Pavel Machek wrote:
> Loop was useless as it would always exit on the first iteration. Fix
> it with right condition.
>
> Signed-off-by: Pavel Machek (CIP)
> Fixes: a86cf9b29e8b ("media: ipu3-cio2: Validate mbus
On Wed, Dec 23, 2020 at 5:26 PM syzbot
wrote:
>
> Hello,
>
> syzbot found the following issue on:
>
> HEAD commit:3644e2d2 mm/filemap: fix infinite loop in generic_file_buf..
> git tree: upstream
> console output: https://syzkaller.appspot.com/x/log.txt?x=16f80eff50
> kernel config:
On Tue, Dec 29, 2020 at 02:04:51PM +0300, Arseny Krasnov wrote:
> To preserve message boundaries, new packet operation was added:
> to mark start of record(with record length in header). To send record,
> packet with start marker is sent first, then all data is transmitted as
> 'RW'
On Wed, Dec 30, 2020 at 03:56:03PM -0500, Michael S. Tsirkin wrote:
> On Tue, Dec 29, 2020 at 02:06:33PM +0300, Arseny Krasnov wrote:
> > This patch simply adds transport ops and removes
> > ignore of non-stream type of packets.
> >
> > Signed-off-by: Arseny Krasnov
>
> How is this supposed
On Tue, Dec 29, 2020 at 02:06:33PM +0300, Arseny Krasnov wrote:
> This patch simply adds transport ops and removes
> ignore of non-stream type of packets.
>
> Signed-off-by: Arseny Krasnov
How is this supposed to work? virtio vsock at the moment
has byte level end to end credit accounting
Add maxim,max8997-battery and maxim,max8997-muic optional nodes.
Signed-off-by: Timon Baetz
Acked-by: Krzysztof Kozlowski
---
v6: No change.
v5: No change.
v4: Make extcon and charger-supply optional.
v3: Reorder patch, no change.
v2: Add patch.
.../bindings/regulator/max8997-regulator.txt
This allows the MAX8997 charger to set the current limit depending on
the detected extcon charger type.
Signed-off-by: Timon Baetz
---
v6: No change.
v5: No change.
v4: No change.
v3: No change.
v2: Remove empty line.
drivers/extcon/extcon-max8997.c | 4
1 file changed, 4 insertions(+)
Value taken from Galaxy S2 Epic 4G Touch SPH-D710 Android vendor
kernel [0] which always sets 200mA.
Also rearrange regulators based on definition in max8997.h.
[0]
Both nodes are disabled as there is no battery and pins are not
connected.
Signed-off-by: Timon Baetz
---
v6: No change.
v5: Add patch.
arch/arm/boot/dts/exynos4210-origen.dts | 10 ++
1 file changed, 10 insertions(+)
diff --git a/arch/arm/boot/dts/exynos4210-origen.dts
muic node is only used for extcon consumers.
charger node is used to point to muic.
Note: charging control is not working as we don't have a charger-supply.
Signed-off-by: Timon Baetz
---
v6: No change.
v5: Add patch.
arch/arm/boot/dts/exynos4210-trats.dts | 9 +
1 file changed, 9
Set CHARGER current and CHARGER_CV voltage according to Galaxy S2 Epic
4G Touch SPH-D710 Android vendor sources [0,1].
Remove regulator-always-on. The regulator can be enabled and disabled
based on extcon events.
[0]
muic node is only used for extcon consumers.
charger node is used to point to muic and regulator.
Signed-off-by: Timon Baetz
---
v6: No change.
v5: No change.
v4: No change.
v3: Reorder patch, no change.
v2: Add patch.
arch/arm/boot/dts/exynos4210-i9100.dts | 10 ++
1 file changed, 10
Register for extcon notification and set charging current depending on
the detected cable type. Current values are taken from vendor kernel,
where most charger types end up setting 650mA [0].
Also enable and disable the CHARGER regulator based on extcon events.
[0]
On Tue, Dec 29, 2020 at 6:59 PM kernel test robot wrote:
>
> [ 235.553325] BUG: sleeping function called from invalid context at
> arch/x86/mm/fault.c:1351
> [ 235.554684] in_atomic(): 0, irqs_disabled(): 1, non_block: 0, pid: 7515,
> name: trinity-c1
> [ 235.555890] 2 locks held by
On Tue, Dec 29, 2020 at 2:07 AM Laurent Pinchart
wrote:
> On Tue, Dec 29, 2020 at 01:54:59AM +0200, Andy Shevchenko wrote:
> > On Tue, Dec 29, 2020 at 1:08 AM Laurent Pinchart wrote:
...
> > +#include
>
> I think this can be dropped.
I dropped above (I noticed it's included by a half of the
When mipi_dsi_attach() fails (e.g. got a -EPROBE_DEFER), the panel should
be removed, otherwise a pointer to it will be kept and then lead to
use-after-free when DRM panel codes are called (e.g. the panel is probed
again).
Fix this by adding cleanup code after mipi_dsi_attach() failure.
Fixes:
850.000,00 Euro wurden Ihnen gerade gespendet.
randconfig-a001-20201229
i386 randconfig-a005-20201230
i386 randconfig-a006-20201230
i386 randconfig-a004-20201230
i386 randconfig-a003-20201230
i386 randconfig-a002-20201230
i386 randconfig-a001-20201230
i386
Greetings,
We are pleased to inform you that an amount of 5000,000.00 (GBP) has
been donated and given to you and your family by Steve & Lenka
Thomson: steve.foundation...@hotmail.com
Regards
Steve Thomson
The pull request you sent on Wed, 30 Dec 2020 18:38:46 +0100:
> https://github.com/ceph/ceph-client.git tags/ceph-for-5.11-rc2
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/f6e1ea19649216156576aeafa784e3b4cee45549
Thank you!
--
Deet-doot-dot, I am a bot.
randconfig-a005-20201230
i386 randconfig-a006-20201230
i386 randconfig-a004-20201230
i386 randconfig-a003-20201230
i386 randconfig-a002-20201230
i386 randconfig-a001-20201230
i386 randconfig-a016
On 30.12.20 19:52, Joe Perches wrote:
> On Wed, 2020-12-30 at 14:36 +0100, Jan Schlien wrote:
>> Hi,
>>
>> I found some odd behavior of checkpatch.pl, which I'm currently using
>> for own projects outside the kernel, but I verified that kernel patches
>> can be affected as well.
>
> Hello Jan.
>
On Wed, Dec 30, 2020 at 03:01:25PM +0800, YANG LI wrote:
> Goto statement jumping will cause lock to be executed again without
> executing unlock, placing the lock statement in front of goto
> label to fix this problem.
>
> Signed-off-by: YANG LI
> Reported-by: Abaci
I am sorry, but have you
> Which shows why it's pointless producing an EEPROM validation tool that
> runs under Linux (as has been your suggestion). They won't use it,
> since their testing only goes as far as "does it work in our product?"
Yes, i would need SNIA to push for conformance testing, hold
plug-testing events,
On Wed, Dec 30, 2020 at 08:30:52PM +0100, Andrew Lunn wrote:
> > Ok!
> >
> > So should we completely skip hwmon_device_register_with_info() call
> > if (i2c_block_size < 2) ?
>
> Yep. That would be a nice simple test.
>
> But does ethtool -m still export the second page? That is also
>
Hello,
syzbot found the following issue on:
HEAD commit:1f45dc22 ibmvnic: continue fatal error reset after passive..
git tree: net
console output: https://syzkaller.appspot.com/x/log.txt?x=10dbe3ff50
kernel config: https://syzkaller.appspot.com/x/.config?x=9c6feb14e07e1220
Hello,
syzbot found the following issue on:
HEAD commit:40f78232 Merge tag 'pci-v5.11-fixes-1' of git://git.kernel..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=1731027750
kernel config: https://syzkaller.appspot.com/x/.config?x=9798d6898fec8a72
> Ok!
>
> So should we completely skip hwmon_device_register_with_info() call
> if (i2c_block_size < 2) ?
Yep. That would be a nice simple test.
But does ethtool -m still export the second page? That is also
unreliable.
Andrew
On Mon 2020-12-14 16:36:21, Rob Herring wrote:
> On Thu, Dec 10, 2020 at 01:54:49PM +0530, Manivannan Sadhasivam wrote:
> > This commit documents the LED triggers used commonly in the SoCs. Not
> > all triggers are documented as some of them are very application specific.
> > Most of the triggers
On Wed, Dec 30, 2020 at 06:31:52PM +0100, Pali Rohár wrote:
> On Wednesday 30 December 2020 17:05:46 Russell King - ARM Linux admin wrote:
> > On Wed, Dec 30, 2020 at 05:56:34PM +0100, Pali Rohár wrote:
> > > This change is really required for those Realtek chips. I thought that
> > > it is
On Wed, Dec 30, 2020 at 06:27:07PM +0100, Marek Behún wrote:
> On Wed, 30 Dec 2020 18:06:52 +0100
> Pali Rohár wrote:
>
> > if (!sfp->type->module_supported() &&
> > (memcmp(id.base.vendor_name, "UBNT", 16) ||
> > memcmp(id.base.vendor_pn, "UF-INSTANT ",
On Wed, Dec 30, 2020 at 06:43:07PM +0100, Pali Rohár wrote:
> On Wednesday 30 December 2020 18:13:15 Andrew Lunn wrote:
> > Hi Pali
> >
> > I have to agree with Russell here. I would rather have no diagnostics
> > than untrustable diagnostics.
>
> Ok!
>
> So should we completely skip
Hi!
> The node names for devices using the pwm-leds driver follow a certain
> naming scheme (now). Parent node name is not enforced, but recommended
> by DT project.
>
> DTC Documentation/devicetree/bindings/mfd/iqs62x.example.dt.yaml
> CHECK
The Intel i210 doesn't work if the Expansion ROM BAR overlaps with
another BAR. Networking won't work at all and once a packet is sent the
netdev watchdog will bite:
[ 89.059374] [ cut here ]
[ 89.064019] NETDEV WATCHDOG: enP2p1s0 (igb): transmit queue 0 timed out
[
On Wed, 2020-12-30 at 14:36 +0100, Jan Schlien wrote:
> Hi,
>
> I found some odd behavior of checkpatch.pl, which I'm currently using
> for own projects outside the kernel, but I verified that kernel patches
> can be affected as well.
Hello Jan.
I've had this patch locally for awhile that I
Hi!
> Apply the same change to led_trigger_blink_setup() as well, since the
> same deadlock scenario can also happen in power_supply_update_bat_leds()
> -> led_trigger_blink() -> led_trigger_blink_setup() (workqueue context),
> and potentially prevent other similar usages.
Thanks, applied.
On 12/19/20 8:36 AM, Sean Young wrote:
clang supports arbitrary length ints using the _ExtInt extension. This
can be useful to hold very large values, e.g. 256 bit or 512 bit types.
Larger types (e.g. 1024 bits) are possible but I am unaware of a use
case for these.
This requires the
On 12/25/20 6:15 PM, William Breathitt Gray wrote:
+Userspace
+-
+Userspace applications can configure Counter events via ioctl operations
+on the Counter character device node. There following ioctl codes are
+supported and provided by the `linux/counter.h` userspace header file:
+
+*
Hi
This patch doesn't handle allocation failure gracefully.
Mikulas
On Tue, 29 Dec 2020, Ignat Korchagin wrote:
> Commit 39d42fa96ba1b7d2544db3f8ed5da8fb0d5cb877 made it possible for some code
> paths in dm-crypt to be executed in softirq context, when the underlying
> driver
> processes IO
Update :
I've just tested the kernel 5.10.4 from ELRepo.
Unfortunately nothing changed - still no sound.
Regards,
Christian
> Thank you Greg,
>
> I am running Fedora 33 with kernel 5.9.16, which works correctly.
> All stable 5.10 versions up to 5.10.3 are having the sound issue.
> Once 5.10.4
On Wed, Dec 30, 2020 at 4:38 PM Daniel Lezcano
wrote:
>
> 32 bits architectures do not support u64 division, so the macro
> DIV_ROUND_CLOSEST is not adequate as the compiler will replace the
> call to an unexisting function for the platform, leading to an
> unresolved symbols.
>
> Fix this by
On Wed 2020-12-30 14:57:08, Lad Prabhakar wrote:
> Use __maybe_unused for the suspend()/resume() hooks and get rid of
> the CONFIG_PM_SLEEP ifdefery to improve the code.
>
> Suggested-by: Pavel Machek
Acked-by: Pavel Machek
> Signed-off-by: Lad Prabhakar
--
DENX Software Engineering GmbH,
Dear Michael,
Thank you for the patch.
Maybe the summary could be more specific:
> PCI: Fix Intel i210 by avoiding overlapping of BARs
Am 30.12.20 um 18:28 schrieb Michael Walle:
The Intel i210 doesn't work if the Expansion ROM BAR overlaps with
another BAR. Networking won't work at all and
On Wed, Dec 30, 2020 at 08:02:52AM -0500, Sasha Levin wrote:
> From: Daniel Rosenberg
>
> [ Upstream commit 7ad08a58bf67594057362e45cbddd3e27e53e557 ]
>
> Expand f2fs's casefolding support to include encrypted directories. To
> index casefolded+encrypted directories, we use the SipHash of the
The Gateworks Venice GW71xx-0x/GW72xx-0x/GW73xx-0x are development
kits comprised of a GW700x SoM and a Baseboard. Future SoM's such
as the GW701x will create additional combinations.
The GW700x SoM contains:
- i.MX 8M Mini SoC
- LPDDR4 DRAM
- eMMC FLASH
- Gateworks System Controller
Add bindings for the Gateworks Venice Development kit boards with
IMX8MM System on Module.
Signed-off-by: Tim Harvey
---
v4: no changes
v3: no changes
v2: no changes
---
Documentation/devicetree/bindings/arm/fsl.yaml | 3 +++
1 file changed, 3 insertions(+)
diff --git
On Wed, Dec 30, 2020 at 07:33:06PM +0200, Oded Gabbay wrote:
> Hi Greg,
>
> This pull request contains a number of important fixes for 5.11-rc2.
> Mainly fixes to support our new F/W with enhanced security features,
> but also additional bugs.
> See details in the tag message below.
>
> Thanks,
The following commit has been merged into the x86/misc branch of tip:
Commit-ID: 4b2d8ca9208be636b30e924b1cbcb267b0740c93
Gitweb:
https://git.kernel.org/tip/4b2d8ca9208be636b30e924b1cbcb267b0740c93
Author:Heiner Kallweit
AuthorDate:Tue, 01 Dec 2020 12:39:57 +01:00
On Wednesday 30 December 2020 18:13:15 Andrew Lunn wrote:
> On Wed, Dec 30, 2020 at 05:05:46PM +, Russell King - ARM Linux admin
> wrote:
> > On Wed, Dec 30, 2020 at 05:56:34PM +0100, Pali Rohár wrote:
> > > This change is really required for those Realtek chips. I thought that
> > > it is
Hi Linus,
The following changes since commit 5c8fe583cce542aa0b84adc939ce85293de36e5e:
Linux 5.11-rc1 (2020-12-27 15:30:22 -0800)
are available in the Git repository at:
https://github.com/ceph/ceph-client.git tags/ceph-for-5.11-rc2
for you to fetch changes up to
On 12/25/20 6:15 PM, William Breathitt Gray wrote:
diff --git a/Documentation/ABI/testing/sysfs-bus-counter-104-quad-8
b/Documentation/ABI/testing/sysfs-bus-counter-104-quad-8
index eac32180c40d..0ecba24d43aa 100644
--- a/Documentation/ABI/testing/sysfs-bus-counter-104-quad-8
+++
Hi Greg,
This pull request contains a number of important fixes for 5.11-rc2.
Mainly fixes to support our new F/W with enhanced security features,
but also additional bugs.
See details in the tag message below.
Thanks,
Oded
The following changes since commit
On Tue, Dec 01, 2020 at 05:38:39PM +0800, shuo.a@intel.com wrote:
> From: Shuo Liu
>
> The Service VM communicates with the hypervisor via conventional
> hypercalls. VMCALL instruction is used to make the hypercalls.
>
> ACRN hypercall ABI:
> * Hypercall number is in R8 register.
> * Up
On Wednesday 30 December 2020 18:17:41 Andrew Lunn wrote:
> On Wed, Dec 30, 2020 at 05:06:23PM +, Russell King - ARM Linux admin
> wrote:
> > On Wed, Dec 30, 2020 at 05:57:58PM +0100, Pali Rohár wrote:
> > > On Wednesday 30 December 2020 16:13:10 Russell King - ARM Linux admin
> > > wrote:
>
On Wednesday 30 December 2020 17:05:46 Russell King - ARM Linux admin wrote:
> On Wed, Dec 30, 2020 at 05:56:34PM +0100, Pali Rohár wrote:
> > This change is really required for those Realtek chips. I thought that
> > it is obvious that from *both* addresses 0x50 and 0x51 can be read only
> > one
Hi Greg,
This pull request contains a number of important fixes for 5.11-rc2.
Mainly fixes to support our new F/W with enhanced security features,
but also additional bugs.
See details in the tag message below.
Thanks,
Oded
The following changes since commit
The Intel i210 doesn't work if the Expansion ROM BAR overlaps with
another BAR. Networking won't work at all and once a packet is sent the
netdev watchdog will bite:
[ 89.059374] [ cut here ]
[ 89.064019] NETDEV WATCHDOG: enP2p1s0 (igb): transmit queue 0 timed out
[
On Wed, 30 Dec 2020 18:06:52 +0100
Pali Rohár wrote:
> if (!sfp->type->module_supported() &&
> (memcmp(id.base.vendor_name, "UBNT", 16) ||
>memcmp(id.base.vendor_pn, "UF-INSTANT ", 16)))
I would rather add a quirk member (bitfield) to the sfp
Sparse will complain about trying to convert between values declared
as snd_ctl_elem_type_t and other types. This patch converts to
consistently use snd_ctl_elem_type_t for control type values. A __force
cast is needed in a couple of cases where the control type value is
parsed out of a DSP data
This fixes some minor cases where u32 or unsigned int types were used
to store big-endian data, and __be32 types used to store both big-endian
and cpu-endian data. This was producing sparse warnings.
Most cases resulted from using the same variable to hold the big-endian
value and its converted
On Wed, Dec 30, 2020 at 05:06:23PM +, Russell King - ARM Linux admin wrote:
> On Wed, Dec 30, 2020 at 05:57:58PM +0100, Pali Rohár wrote:
> > On Wednesday 30 December 2020 16:13:10 Russell King - ARM Linux admin wrote:
> > > On Wed, Dec 30, 2020 at 04:47:54PM +0100, Pali Rohár wrote:
> > > >
During SSR after memory dump collection,BT controller will be powered off,
powered on and then FW will be downloaded.During suspend if BT controller
is powered off due to SSR then we should wait until SSR is completed and
then suspend.
Fixes: 2be43abac5a8 ("Bluetooth: hci_qca: Wait for timeout
On Wed, Dec 30, 2020 at 05:05:46PM +, Russell King - ARM Linux admin wrote:
> On Wed, Dec 30, 2020 at 05:56:34PM +0100, Pali Rohár wrote:
> > This change is really required for those Realtek chips. I thought that
> > it is obvious that from *both* addresses 0x50 and 0x51 can be read only
> >
On Wed, Dec 30, 2020 at 05:57:58PM +0100, Pali Rohár wrote:
> On Wednesday 30 December 2020 16:13:10 Russell King - ARM Linux admin wrote:
> > On Wed, Dec 30, 2020 at 04:47:54PM +0100, Pali Rohár wrote:
> > > Some GPON SFP modules (e.g. Ubiquiti U-Fiber Instant) have set both
> > >
On Wednesday 30 December 2020 16:11:51 Russell King - ARM Linux admin wrote:
> On Wed, Dec 30, 2020 at 04:47:53PM +0100, Pali Rohár wrote:
> > Some GPON SFP modules (e.g. Ubiquiti U-Fiber Instant) have set SFF phys_id
> > in their EEPROM. Kernel SFP subsystem currently does not allow to use
> >
On Wed, Dec 30, 2020 at 05:56:34PM +0100, Pali Rohár wrote:
> This change is really required for those Realtek chips. I thought that
> it is obvious that from *both* addresses 0x50 and 0x51 can be read only
> one byte at the same time. Reading 2 bytes (for be16 value) cannot be
> really done by
This function is used to handle errors which may cause data lost in
filesystem. Such as memory failure in fsdax mode.
In XFS, it requires "rmapbt" feature in order to query for files or
metadata which associated to the corrupted data. Then we could call fs
recover functions to try to repair the
With the support of ->rmap(), it is possible to obtain the superblock on
a mapped device.
If a pmem device is used as one target of mapped device, we cannot
obtain its superblock directly. With the help of SYSFS, the mapped
device can be found on the target devices. So, we iterate the
Since owner tarcking is triggerred by pmem device, these functions are
useless. So remove it.
Signed-off-by: Shiyang Ruan
---
fs/dax.c| 112
include/linux/dax.h | 2 -
2 files changed, 114 deletions(-)
diff --git a/fs/dax.c b/fs/dax.c
Call the ->memory_failure() which is implemented by pmem driver, in
order to finally notify filesystem to handle the corrupted data. The
old collecting and killing processes are moved into
mf_dax_mapping_kill_procs(), which will be called by filesystem.
Signed-off-by: Shiyang Ruan
---
Pmem device could be a target of mapped device. In order to obtain
superblock on the mapped device, we introduce this to translate offset
from target device to md device.
Currently, we implement it on linear target, which is easy to do the
translation. Other targets will be supported in the
Obtain the superblock of a pmem disk, and call filesystem's
->corrupted_range() to handle the corrupted data.
Signed-off-by: Shiyang Ruan
---
block/genhd.c | 12
drivers/nvdimm/pmem.c | 24
include/linux/genhd.h | 1 +
3 files changed, 37
The current memory_failure_dev_pagemap() can only handle single-mapped
dax page for fsdax mode. The dax page could be mapped by multiple files
and offsets if we let reflink feature & fsdax mode work together. So,
we refactor current implementation to support handle memory failure on
each file
In fsdax mode, the memory failure happens on block device. So, it is
needed to introduce an interface for block devices. Each kind of block
device can handle the memory failure in ther own ways.
Signed-off-by: Shiyang Ruan
---
include/linux/blkdev.h | 2 ++
1 file changed, 2 insertions(+)
This patchset is aimed to support shared pages tracking for fsdax.
Change from RFC v3:
- Do not lock dax entry in memory failure handler
- Add a helper function for corrupted_range
- Add restrictions in xfs code
- Fix code style
- remove the useless association and lock in fsdax
Change
When memory-failure occurs, we call this function which is implemented
by each kind of devices. For the fsdax case, pmem device driver
implements it. Pmem device driver will find out the block device where
the error page locates in, and try to get the filesystem on this block
device. And
Memory failure occurs in fsdax mode will finally be handled in
filesystem. We introduce this interface to find out files or metadata
affected by the corrupted range, and try to recover the corrupted data
if possiable.
Signed-off-by: Shiyang Ruan
---
include/linux/fs.h | 2 ++
1 file changed, 2
On Wednesday 30 December 2020 16:13:10 Russell King - ARM Linux admin wrote:
> On Wed, Dec 30, 2020 at 04:47:54PM +0100, Pali Rohár wrote:
> > Some GPON SFP modules (e.g. Ubiquiti U-Fiber Instant) have set both
> > SFP_OPTIONS_LOS_INVERTED and SFP_OPTIONS_LOS_NORMAL bits in their EEPROM.
> >
> >
DesignWare core has a TLP digest (TD) override bit in one of the control
registers of ATU. This bit also needs to be programmed for proper ECRC
functionality. This is currently identified as an issue with DesignWare
IP version 4.90a.
Signed-off-by: Vidya Sagar
Acked-by: Bjorn Helgaas
---
V3:
*
On Wednesday 30 December 2020 16:10:37 Russell King - ARM Linux admin wrote:
> On Wed, Dec 30, 2020 at 04:47:52PM +0100, Pali Rohár wrote:
> > Workaround for GPON SFP modules based on VSOL V2801F brand was added in
> > commit 0d035bed2a4a ("net: sfp: VSOL V2801F / CarlitoxxPro CPGOS03-0490
> >
On 30.12.20 03:46, Hillf Danton wrote:
On Wed, 30 Dec 2020 00:56:27 +0100
Threads, which committed items to the CIL, wait in the xc_push_wait
waitqueue when used_space in the push context goes over a limit. These
threads need to be woken when the CIL is pushed.
The CIL push worker tries to
On 30.12.2020 17:15, Florian Fainelli wrote:
>
>
> On 12/30/2020 1:12 AM, Heiner Kallweit wrote:
>> On 30.12.2020 10:07, DENG Qingfang wrote:
>>> Hi Heiner,
>>> Thanks for your reply.
>>>
>>> On Wed, Dec 30, 2020 at 3:39 PM Heiner Kallweit
>>> wrote:
I don't think that's the best option.
On 12/30/20 12:15 AM, Freddy Hsin wrote:
> From: "freddy.hsin"
>
> Before user space daemon start to access the watchdog device,
> there is a time interval that watchdog is disabled in the
> original flow. If the system freezing at this interval, it
> cannot be rebooted by watchdog hardware
On Wed, Dec 30, 2020 at 4:40 PM wrote:
> From: Guo Ren
>
> Pick up the patch from the 'Link' made by Mark Rutland. Keep the
> same with x86, arm, arm64, arc, sh, power.
>
> Link:
> https://lore.kernel.org/linux-arm-kernel/1499782763-31418-1-git-send-email-mark.rutl...@arm.com/
> Signed-off-by:
On Tue, Dec 22, 2020 at 03:30:11PM +0100, Robert Marko wrote:
> Add basic monitoring support as well as port on/off control for Texas
> Instruments TPS23861 PoE PSE IC.
>
> Signed-off-by: Robert Marko
> Cc: Luka Perkov
> ---
> Changes in v3:
> * Leave only standard values in hwmon hwmon
> *
On Wed, Dec 30, 2020 at 10:33:09AM +, Charles Keepax wrote:
> A new flag MACB_CAPS_CLK_HW_CHG was added and all callers of
> macb_set_tx_clk were gated on the presence of this flag.
>
> - if (!clk)
> + if (!bp->tx_clk || !(bp->caps & MACB_CAPS_CLK_HW_CHG))
>
> However the flag was not
On Wed, Dec 30, 2020 at 12:48:32AM -0800, Praveen Chaudhary wrote:
> Allow user to set metric on default route learned via Router Advertisement.
> Not: RFC 4191 does not say anything for metric for IPv6 default route.
Hi Praveen
Please take a look at
On Wed, Dec 30, 2020 at 5:14 AM Mark Brown wrote:
>
> On Tue, Dec 29, 2020 at 08:23:00AM -0800, Tim Harvey wrote:
> > On Tue, Dec 29, 2020 at 5:06 AM Mark Brown wrote:
>
> > > I can't understand what this commit message is trying to say, sorry.
> > > Which bits are you talking about when you say
850.000,00 Euro wurden Ihnen gespendet
On 12/30/20 5:57 PM, Lad Prabhakar wrote:
> Replace C++ style comment with C style.
Note that the switch to // was made following the SPI maintainer's request...
> Signed-off-by: Lad Prabhakar
[...]
MBR, Sergei
From: Moti Haimovski
DRAM physical page sizes depend of the amount of HBMs available in
the device. this number is device-dependent and may also be subject
to binning when one or more of the DRAM controllers are found to
to be faulty. Such a configuration may lead to partitioning the DRAM
to
From: Ofir Bitton
Accessing kernel allocated memory through debugfs should not
be allowed as it introduces a security vulnerability.
We remove the option to read/write kernel memory for all asics.
Signed-off-by: Ofir Bitton
Reviewed-by: Oded Gabbay
Signed-off-by: Oded Gabbay
---
On 12/30/2020 7:16 AM, Andrew Lunn wrote:
>> 2. Allocated ds->slave_mii_bus before calling ds->ops->setup, because
>> we cannot call dsa_slave_mii_bus_init which is private.
>>
>> Any better ideas?
>
> Do what mv88e6xxx does, allocate the MDIO bus inside the switch
> driver.
Yes, exactly, or
On Wed, Dec 30, 2020 at 08:00:38PM +0800, qiang.zh...@windriver.com wrote:
> From: Zqiang
>
> Due to freeary function is called with spinlock be held,
> the synchronize_rcu function may be called in kfree_rcu
> function, the schedule may be happen in spinlock critical
> region, need to replace
On Wed, 30 Dec 2020 at 16:47, Arnd Bergmann wrote:
>
> From: Arnd Bergmann
>
> Building ubsan kernels even for compile-testing introduced these
> warnings in my randconfig environment:
>
> crypto/blake2b_generic.c:98:13: error: stack frame size of 9636 bytes in
> function 'blake2b_compress'
101 - 200 of 485 matches
Mail list logo
