.
We currently have no Qualcomm hardware in the Xen Project test lab so
we do not need this enabled.
CC: Julien Grall
CC: linux-arm-...@vger.kernel.org
CC: linux-kernel@vger.kernel.org
CC: Stephen Boyd
CC: Andy Gross
CC: Bjorn Andersson
CC: Avaneesh Kumar Dwivedi
Signed-off-by: Ian Jackson
--
Stephen Boyd writes ("[PATCH 1/3] firmware: qcom_scm: Use proper types for dma
mappings"):
> We need to use the proper types and convert between physical addresses
> and dma addresses here to avoid mismatch warnings. This is especially
> important on systems with a different size for dma addresses
Julien Grall writes ("qcom_scm: Incompatible pointer type build failure"):
> Thank you for the report.
...>
> On 30/04/2019 13:44, Ian Jackson wrote:
> > osstest service owner writes ("[linux-4.19 test] 135420: regressions -
> > FAIL"):
> >
osstest service owner writes ("[linux-linus bisection] complete
build-i386-pvops"):
> branch xen-unstable
> xenbranch xen-unstable
> job build-i386-pvops
> testid kernel-build
>
> Tree: linux
> git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git
> Tree: linuxfirmware git://xenbi
I see that linux-4.1.y is still at 5880876e9469 which has the serious
bug introduced by the backport c5ad33184354 "mm/swap.c: flush lru
pvecs on compound page arrival".
The analogous problem is also still affecting at least linux-3.18.y.
Is there some problem with reverting this patch in the stab
Luis R. Rodriguez writes ("Wiki for automatic reports / fixes"):
[...]
> While discussing expectations and information about
> reports over these with Valentin it occurred to me information about
> all these may be scattered separately and some developers may be
> surprised when they first get rep
Julian Calaby writes ("Re: [PATCH] [SCSI] libsas: Kconfig: Enable SATA
compatibility by default"):
> On Sat, May 2, 2015 at 12:36 AM, Ian Jackson
> wrote:
> > SATA controllers support SATA disks. The kernel should be able to
>
> Do you mean SAS controllers?
Ye
SATA controllers support SATA disks. The kernel should be able to
drive these, by default. It should not silently (apart from a
debugging-only printk) ignore them.
Signed-off-by: Ian Jackson
CC: James Bottomley
CC: Donald D Dugger
CC: Pawel Baldysiak
CC: Lukasz Dorau
CC: Artur Paszkiewicz
Ian Jackson writes ("Re: [Xen-devel] [PATCH 09/10] xen/swiotlb: Fix compile
warnings when using plain integer instead of NULL pointer."):
> Oh wait this is Linux kernel code, not in Xen? Still,
> Documentation/CodingStyle doesn't say that NULL is required.
Someone on irc fo
Ian Jackson writes ("Re: [Xen-devel] [PATCH 09/10] xen/swiotlb: Fix compile
warnings when using plain integer instead of NULL pointer."):
> Konrad Rzeszutek Wilk writes ("[Xen-devel] [PATCH 09/10] xen/swiotlb: Fix
> compile warnings when using plain integer instead of NULL
Konrad Rzeszutek Wilk writes ("[Xen-devel] [PATCH 09/10] xen/swiotlb: Fix
compile warnings when using plain integer instead of NULL pointer."):
> arch/x86/xen/pci-swiotlb-xen.c:96:1: warning: Using plain integer as NULL
> pointer
> arch/x86/xen/pci-swiotlb-xen.c:96:1: warning: Using plain integer
I recently tried out 2.2.19pre10 because of the VM problems with
2.2.18. The system lasted about 10 hours and then paniced. On the
console was:
chiark login: kernel panic: skput: over: cD158117:3872 put:3872 dev:10
S13 Transmit timed out, bad line quality?
S13 Transmit timed out, bad line
Andrea Arcangeli writes ("Re: linux 2.2.18pre17 + VM-global -7 = `Negative d_count'
oops"):
> On Thu, Oct 26, 2000 at 06:37:37PM +0100, Ian Jackson wrote:
> > Negative d_count (-805538369) for [binary garbage]/
> >
> > followed by an oops. Kernel logfile e
Andrea Arcangeli writes ("Re: linux 2.2.18-pre17: "Kernel panic: LRU list corrupted""):
> I also included the fix in a new VM-global patch against vanilla 2.2.18pre17
> (the VM-global patch is available as a single patch inside 2.2.18pre17aa1/
> directory too but I have to maintain a separate vers
14 matches
Mail list logo
