~vicamo/+git/ubuntu-kernel:bug-1886247/add-8822ce-0xc82f/unstable

Branch merges

Related source package recipes

No recipes using this branch. (?)

Create packaging recipe

Related snap packages

Related charm recipes

d078668... by You-Sheng Yang on 2020-07-07

Bug 1886247: rtw88: 8822ce: add support for device ID 0xc82f

14f6f06... by AaronMa on 2020-06-12

rtw88: 8822ce: add support for device ID 0xc82f

BugLink: https://bugs.launchpad.net/bugs/1886247

New device ID 0xc82f found on Lenovo ThinkCenter.
Tested it with c822 driver, works good.

PCI id:
03:00.0 Network controller [0280]: Realtek Semiconductor Co., Ltd.
Device [10ec:c82f]
        Subsystem: Lenovo Device [17aa:c02f]

Signed-off-by: Aaron Ma <email address hidden>
(backported from
https://<email address hidden>/raw)
Signed-off-by: You-Sheng Yang <email address hidden>

c5373fb... by Paolo Pisati on 2020-07-06

UBUNTU: Ubuntu-5.7-5.7.0-15.16

Signed-off-by: Paolo Pisati <email address hidden>

c351dd5... by Paolo Pisati on 2020-07-06

UBUNTU: Start new release

Ignore: yes
Signed-off-by: Paolo Pisati <email address hidden>

887432c... by Sasha on 2020-06-30

Linux 5.7.7

BugLink: https://bugs.launchpad.net/bugs/1886395

Signed-off-by: Sasha Levin <email address hidden>
Signed-off-by: Paolo Pisati <email address hidden>

e136789... by Greg Kroah-Hartman <email address hidden> on 2020-05-12

Revert "tty: hvc: Fix data abort due to race in hvc_open"

BugLink: https://bugs.launchpad.net/bugs/1886395

commit cf9c94456ebafc6d75a834e58dfdc8ae71a3acbc upstream.

This reverts commit e2bd1dcbe1aa34ff5570b3427c530e4332ecf0fe.

In discussion on the mailing list, it has been determined that this is
not the correct type of fix for this issue. Revert it so that we can do
this correctly.

Reported-by: Jiri Slaby <email address hidden>
Reported-by: Greg Kroah-Hartman <email address hidden>
Link: https://<email address hidden>
Cc: Raghavendra Rao Ananta <email address hidden>
Signed-off-by: Greg Kroah-Hartman <email address hidden>

Signed-off-by: Paolo Pisati <email address hidden>

47ef175... by Mikulas Patocka <email address hidden> on 2020-06-19

dm writecache: add cond_resched to loop in persistent_memory_claim()

BugLink: https://bugs.launchpad.net/bugs/1886395

commit d35bd764e6899a7bea71958f08d16cea5bfa1919 upstream.

Add cond_resched() to a loop that fills in the mapper memory area
because the loop can be executed many times.

Fixes: 48debafe4f2fe ("dm: add writecache target")
Cc: <email address hidden>
Signed-off-by: Mikulas Patocka <email address hidden>
Signed-off-by: Mike Snitzer <email address hidden>
Signed-off-by: Greg Kroah-Hartman <email address hidden>

Signed-off-by: Paolo Pisati <email address hidden>

bedde76... by Huaisheng ye on 2020-06-12

dm writecache: correct uncommitted_block when discarding uncommitted entry

BugLink: https://bugs.launchpad.net/bugs/1886395

commit 39495b12ef1cf602e6abd350dce2ef4199906531 upstream.

When uncommitted entry has been discarded, correct wc->uncommitted_block
for getting the exact number.

Fixes: 48debafe4f2fe ("dm: add writecache target")
Cc: <email address hidden>
Signed-off-by: Huaisheng Ye <email address hidden>
Acked-by: Mikulas Patocka <email address hidden>
Signed-off-by: Mike Snitzer <email address hidden>
Signed-off-by: Greg Kroah-Hartman <email address hidden>

Signed-off-by: Paolo Pisati <email address hidden>

5d95d70... by Charles Lever on 2020-06-15

xprtrdma: Fix handling of RDMA_ERROR replies

BugLink: https://bugs.launchpad.net/bugs/1886395

commit 7b2182ec381f8ea15c7eb1266d6b5d7da620ad93 upstream.

The RPC client currently doesn't handle ERR_CHUNK replies correctly.
rpcrdma_complete_rqst() incorrectly passes a negative number to
xprt_complete_rqst() as the number of bytes copied. Instead, set
task->tk_status to the error value, and return zero bytes copied.

In these cases, return -EIO rather than -EREMOTEIO. The RPC client's
finite state machine doesn't know what to do with -EREMOTEIO.

Additional clean ups:
- Don't double-count RDMA_ERROR replies
- Remove a stale comment

Signed-off-by: Chuck Lever <email address hidden>
Cc: <email address hidden>
Signed-off-by: Anna Schumaker <email address hidden>
Signed-off-by: Greg Kroah-Hartman <email address hidden>

Signed-off-by: Paolo Pisati <email address hidden>

e2aaec3... by Borislav Petkov <email address hidden> on 2020-06-18

EDAC/amd64: Read back the scrub rate PCI register on F15h

BugLink: https://bugs.launchpad.net/bugs/1886395

commit ee470bb25d0dcdf126f586ec0ae6dca66cb340a4 upstream.

Commit:

  da92110dfdfa ("EDAC, amd64_edac: Extend scrub rate support to F15hM60h")

added support for F15h, model 0x60 CPUs but in doing so, missed to read
back SCRCTRL PCI config register on F15h CPUs which are *not* model
0x60. Add that read so that doing

  $ cat /sys/devices/system/edac/mc/mc0/sdram_scrub_rate

can show the previously set DRAM scrub rate.

Fixes: da92110dfdfa ("EDAC, amd64_edac: Extend scrub rate support to F15hM60h")
Reported-by: Anders Andersson <email address hidden>
Signed-off-by: Borislav Petkov <email address hidden>
Cc: <email address hidden> #v4.4..
Link: https://lkml.<email address hidden>
Signed-off-by: Greg Kroah-Hartman <email address hidden>

Signed-off-by: Paolo Pisati <email address hidden>