rd().
Fixes: e056a1b5b67b ("mmc: queue: let host controllers specify
maximum discard timeout")
Fixes: b35fd7422c2f ("block: check queue's
limits.discard_granularity in __blkdev_issue_discard()").
Reported-by: Vicente Bergas
Signed-off-by: Coly Li
Acked-by: Adrian Hunte
On Thu, Oct 1, 2020 at 11:07 AM Adrian Hunter wrote:
>
> On 1/10/20 11:38 am, Vicente Bergas wrote:
> > On Thu, Oct 1, 2020 at 9:18 AM Coly Li wrote:
> >>
> >> In mmc_queue_setup_discard() the mmc driver queue's discard_granularity
> >> might be set as
n __blkdev_issue_discard()"), a "Fixes:" tag
> is also added for the commit to make sure people won't miss this patch
> after applying the change of __blkdev_issue_discard().
>
> Fixes: e056a1b5b67b ("mmc: queue: let host controllers specify maximum
> discard timeout&qu
On Saturday, October 5, 2019 2:52:00 AM CEST, Vivek Unune wrote:
On Fri, Oct 04, 2019 at 11:45:08PM +0200, Heiko Stuebner wrote:
Hi Vivek,
Am Montag, 30. September 2019, 01:46:15 CEST schrieb Vivek Unune: ...
Hi Heiko,
I tested the c09b73cf patch without modifying exsisting dts. I can
On Sunday, September 29, 2019 5:22:30 AM CEST, Vivek Unune wrote:
Fix usb-c on X99 TV Box. Tested with armbian w/ kernel 5.3
Signed-off-by: Vivek Unune
---
arch/arm64/boot/dts/rockchip/rk3399-hugsun-x99.dts | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git
On Tuesday, June 25, 2019 12:48:17 PM CEST, Vicente Bergas wrote:
On Tuesday, June 25, 2019 11:46:02 AM CEST, Will Deacon wrote:
[+Marc]
Hi again, Vicente,
On Mon, Jun 24, 2019 at 12:47:41PM +0100, Will Deacon wrote: ...
Hi Will,
the memtest test is still pending...
Hi Will,
i've just ran
On Tuesday, June 25, 2019 11:46:02 AM CEST, Will Deacon wrote:
[+Marc]
Hi again, Vicente,
On Mon, Jun 24, 2019 at 12:47:41PM +0100, Will Deacon wrote:
On Sat, Jun 22, 2019 at 08:02:19PM +0200, Vicente Bergas wrote: ...
Before you rush over to LAKML, please could you provide your full dmesg
. Should this be redirected
somewhere else now?
Regards,
Vicenç.
On Wednesday, June 19, 2019 7:09:40 PM CEST, Al Viro wrote:
On Wed, Jun 19, 2019 at 06:51:51PM +0200, Vicente Bergas wrote:
What's your config, BTW? SMP and DEBUG_SPINLOCK, specifically...
Hi Al,
here it is:
https
On Wednesday, June 19, 2019 6:28:02 PM CEST, Al Viro wrote:
[arm64 maintainers Cc'd; I'm not adding a Cc to moderated list,
sorry]
On Wed, Jun 19, 2019 at 02:42:16PM +0200, Vicente Bergas wrote:
Hi Al,
i have been running the distro-provided kernel the last few weeks
and had no issues at all
On Tuesday, June 18, 2019 8:35:48 PM CEST, Al Viro wrote:
On Tue, May 28, 2019 at 11:38:43AM +0200, Vicente Bergas wrote:
On Wednesday, May 22, 2019 6:29:46 PM CEST, Al Viro wrote: ...
__d_lookup() running into >d_hash == 0x0100 at some
point in hash chain
and trying to l
On Wednesday, May 22, 2019 6:29:46 PM CEST, Al Viro wrote:
...
IOW, here we have also run into bogus hlist forward pointer or head -
same 0x100 in one case and 0x88000100 in two others.
Have you tried to see if KASAN catches anything on those loads?
Use-after-free, for example...
On Wednesday, May 22, 2019 6:29:46 PM CEST, Al Viro wrote:
On Wed, May 22, 2019 at 05:44:30PM +0200, Vicente Bergas wrote:
...
IOW, here we have also run into bogus hlist forward pointer or head -
same 0x100 in one case and 0x88000100 in two others.
Have you tried to see if KASAN
Hi Al,
On Wednesday, May 22, 2019 3:53:31 PM CEST, Al Viro wrote:
On Wed, May 22, 2019 at 12:40:55PM +0200, Vicente Bergas wrote:
Hi,
since a recent update the kernel is reporting d_lookup errors.
They appear randomly and after each error the affected file or directory
is no longer accessible
Hi,
since a recent update the kernel is reporting d_lookup errors.
They appear randomly and after each error the affected file or directory
is no longer accessible.
The kernel is built with GCC 9.1.0 on ARM64.
Four traces from different workloads follow.
This trace is from
On Sunday, April 7, 2019 2:57:59 AM CEST, Vicente Bergas wrote:
This reverts
commit 420b82f84294 ("spi: rockchip: set min/max speed")
commit 74b7efa82b11 ("spi: rockchip: precompute rx sample delay")
The former breaks bursts of writes of 48 bytes or more.
Both patches
On Sunday, April 7, 2019 9:55:10 PM CEST, Emil Renner Berthing wrote:
Hi Vicente,
On Sat, 6 Apr 2019 at 19:35, Vicente Bergas wrote:
Hi,
i have been experiencing issues writing to NOR-Flash SPI Memories
from two RK3399-based platforms: gru-kevin and sapphire board.
For kevin, this resulted
the first. Reverting both just results in an easy to fix
conflict.
Tested-by: Vicente Bergas
Signed-off-by: Vicente Bergas
---
drivers/spi/spi-rockchip.c | 80 ++
1 file changed, 46 insertions(+), 34 deletions(-)
diff --git a/drivers/spi/spi-rockchip.c b/driver
allows
us let the spi framework handle min/max speeds
for us.
Regards,
Vicenç.
On Saturday, April 6, 2019 7:34:32 PM CEST, Vicente Bergas wrote:
Hi,
i have been experiencing issues writing to NOR-Flash SPI Memories
from two RK3399-based platforms: gru-kevin and sapphire board.
For kevin
dd8fd2cbc73f8650f651da71fc61a6e4f30c1566
Regards,
Vicenç.
On Saturday, April 6, 2019 7:34:32 PM CEST, Vicente Bergas wrote:
Hi,
i have been experiencing issues writing to NOR-Flash SPI Memories
from two RK3399-based platforms: gru-kevin and sapphire board.
For kevin, this resulted in a bricked device because
Hi,
i have been experiencing issues writing to NOR-Flash SPI Memories
from two RK3399-based platforms: gru-kevin and sapphire board.
For kevin, this resulted in a bricked device because that memory
is the only boot device.
Fortunately an external programmer is available.
In order to isolate
On Tue, Sep 4, 2018 at 5:45 PM, Chao Yu wrote:
> On 2018/9/4 23:25, Vicente Bergas wrote:
>> On Mon, Sep 3, 2018 at 9:52 PM, Chao Yu wrote:
>>> From: Chao Yu
>>>
>>> https://nam01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbugzilla.kernel.org%2Fshow_
On Tue, Sep 4, 2018 at 5:45 PM, Chao Yu wrote:
> On 2018/9/4 23:25, Vicente Bergas wrote:
>> On Mon, Sep 3, 2018 at 9:52 PM, Chao Yu wrote:
>>> From: Chao Yu
>>>
>>> https://nam01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbugzilla.kernel.org%2Fshow_
ssage appears a few times:
>
> dwc3: failed to initialize core
>
> The driver is deferred waiting for the typec-phy, but this never happens
> bceause is disabled. So, enable it.
>
> Fixes: c301b327aea898af ("arm64: dts: rockchip: add usb3-phy otg-port support
> for rk3
>
> dwc3: failed to initialize core
>
> The driver is deferred waiting for the typec-phy, but this never happens
> bceause is disabled. So, enable it.
>
> Fixes: c301b327aea898af ("arm64: dts: rockchip: add usb3-phy otg-port support
> for rk3399")
> Reported-by:
24 matches
Mail list logo
