On Mon, 15 Aug 2022, Geert Uytterhoeven wrote:
Below is the list of build error/warning regressions/improvements in
v6.0-rc1[1] compared to v5.19[2].
Summarized:
- build errors: +26/-15
+ /kisskb/src/arch/parisc/kernel/vdso32/restart_syscall.S: Error: .cfi_endproc
without corresponding
Hi Marc,
On Wed, May 26, 2021 at 10:32 AM Marc Zyngier wrote:
> On Wed, 26 May 2021 09:18:27 +0100,
> Geert Uytterhoeven wrote:
> > On Wed, May 26, 2021 at 10:01 AM Marc Zyngier wrote:
> > > On Wed, 26 May 2021 08:52:42 +0100,
> > > Geert Uytterhoeven wrote:
>
Hi Marc,
On Wed, May 26, 2021 at 10:01 AM Marc Zyngier wrote:
> On Wed, 26 May 2021 08:52:42 +0100,
> Geert Uytterhoeven wrote:
> > On Tue, May 11, 2021 at 11:13 AM Marc Zyngier wrote:
> > > On 2021-05-11 10:07, Geert Uytterhoeven wrote:
> > > > On Tue, Mar
Hi Marc,
On Tue, May 11, 2021 at 11:13 AM Marc Zyngier wrote:
> On 2021-05-11 10:07, Geert Uytterhoeven wrote:
> > On Tue, Mar 30, 2021 at 4:56 PM Marc Zyngier wrote:
> >> From: Jianyong Wu
> >>
> >> Currently, there is no mechanism to keep time sync bet
) || (HAVE_ARM_SMCCC_DISCOVERY &&
> ARM_ARCH_TIMER)
Why does this not depend on KVM_GUEST on ARM?
I.e. shouldn't the dependency be:
KVM_GUEST && (X86 || (HAVE_ARM_SMCCC_DISCOVERY && ARM_ARCH_TIMER))
?
> default y
> help
>
On Wed, Apr 14, 2021 at 3:53 PM Marc Zyngier wrote:
> perf_pmu_name() and perf_num_counters() are unused. Drop them.
>
> Signed-off-by: Marc Zyngier
Reviewed-by: Geert Uytterhoeven
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Lin
r_err("CPU%u: %s", smp_processor_id(), msg);
pr_alert(), to match the patch description.
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- ge...@linux-m68k.org
In personal conversations with technical people
tion for
>> gcc earlier than 4.3.
>
> This sounds good to me!
+1
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- ge...@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
oesn't have this particular bug, or it was a regression between
> gcc-4.1.2 and 4.1.3.
Mine is also some patched version of 4.1.1, built from Ubuntu sources:
gcc version 4.1.2 20061115 (prerelease) (Ubuntu 4.1.1-21)
These sources probably even contained the fixes to make gcc-4.1.1
usable
Hi Arnd,
On Mon, Apr 24, 2017 at 11:44 AM, Arnd Bergmann wrote:
> On Sun, Apr 23, 2017 at 10:13 PM, Geert Uytterhoeven
> wrote:
>> On Sat, Apr 22, 2017 at 5:30 PM, Arnd Bergmann wrote:
>>> Based on what I found so far, gcc-4 can be pretty much ruled out from
>>> b
rgd, .bii = 0, .offset = 0 };
+ struct gfs2_rbm rbm = { .bii = 0, .offset = 0 };
+ rbm.rgd = rgd;
+
while (1) {
down_write(&sdp->sd_log_flush_lock);
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux b
Hi Arnd,
On Fri, Dec 16, 2016 at 8:58 PM, Arnd Bergmann wrote:
> On Friday, December 16, 2016 4:54:33 PM CET Geert Uytterhoeven wrote:
>> On Fri, Dec 16, 2016 at 11:56 AM, Arnd Bergmann wrote:
>> > Specifically on ARM, going further makes things rather useless especially
>
-gcc-4.1.2
and looking at the compiler warnings for years, so I only have to look
at new warnings.
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- ge...@linux-m68k.org
In personal conversations with technical people, I call
13 matches
Mail list logo
