qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Cornelia Huck <cohuck@redhat.com>
To: Aleksandar Markovic <aleksandar.m.mail@gmail.com>
Cc: Riku Voipio <riku.voipio@iki.fi>,
	Laurent Vivier <laurent@vivier.eu>,
	"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
	"qemu-s390x@nongnu.org" <qemu-s390x@nongnu.org>,
	Aleksandar Markovic <amarkovic@wavecomp.com>,
	Aleksandar Rikalo <aleksandar.rikalo@rt-rk.com>,
	Aurelien Jarno <aurelien@aurel32.net>
Subject: Linux headers updates (was: Re: [PATCH 00/22] linux-user: generate syscall_nr.sh)
Date: Tue, 18 Feb 2020 18:56:38 +0100	[thread overview]
Message-ID: <20200218185638.7a626b30.cohuck@redhat.com> (raw)
In-Reply-To: <CAL1e-=hSSeOi9+sHofSpqPyBU_o2O0GHjBbc91eZRyBGSg==mA@mail.gmail.com>

On Tue, 18 Feb 2020 18:46:54 +0100
Aleksandar Markovic <aleksandar.m.mail@gmail.com> wrote:

> On Tuesday, February 18, 2020, Cornelia Huck <cohuck@redhat.com> wrote:

> > That said, I'll probably queue a headers update on the s390-next branch
> > right now (against current Linus master),  
> 
> 
> >  
> Hi, Cornelia,
> 
> I am not stopping you from updating headers from Linus' master, however, I
> think a better practice would be to do regular updates from each stable
> kernel release (the last one is 5.5), rather than from an arbitrary
> kernel-du-jour, which may be the subject of change (including reverts) wrt
> headers between two stable releases.

I disagree. Not being able to do an update for a whole three months
would block any of the features relying on kernel interfaces for the
same time (or even longer, if the kernel release schedule aligns badly
with QEMU freeze.)

Issues with things being reverted in the Linux headers have been rare
(and the ones I remember were because we did not merge from Linus
master, but from some other tree that changed before being merged). I
don't think it is worth slowing down development because of those rare
issues.



  reply	other threads:[~2020-02-18 17:57 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-17 22:35 [PATCH 00/22] linux-user: generate syscall_nr.sh Laurent Vivier
2020-02-17 22:35 ` [PATCH 01/22] linux-user: introduce parameters to generate syscall_nr.h Laurent Vivier
2020-02-17 22:35 ` [PATCH 02/22] linux-user,alpha: add syscall table generation support Laurent Vivier
2020-02-17 22:35 ` [PATCH 03/22] linux-user,hppa: " Laurent Vivier
2020-02-17 22:35 ` [PATCH 04/22] linux-user,m68k: " Laurent Vivier
2020-02-17 22:35 ` [PATCH 05/22] linux-user, xtensa: " Laurent Vivier
2020-02-17 22:35 ` [PATCH 06/22] linux-user,sh4: " Laurent Vivier
2020-02-17 22:35 ` [PATCH 07/22] linux-user, microblaze: " Laurent Vivier
2020-02-17 22:35 ` [PATCH 08/22] linux-user,arm: " Laurent Vivier
2020-02-18 14:11   ` Laurent Vivier
2020-02-17 22:35 ` [PATCH 09/22] linux-user,ppc: split syscall_nr.h Laurent Vivier
2020-02-17 22:35 ` [PATCH 10/22] linux-user,ppc: add syscall table generation support Laurent Vivier
2020-02-17 22:35 ` [PATCH 11/22] linux-user, s390x: remove syscall definitions for !TARGET_S390X Laurent Vivier
2020-02-17 22:35 ` [PATCH 12/22] linux-user,s390x: add syscall table generation support Laurent Vivier
2020-02-17 22:35 ` [PATCH 13/22] linux-user, sparc, sparc64: " Laurent Vivier
2020-02-17 22:35 ` [PATCH 14/22] linux-user,i386: " Laurent Vivier
2020-02-17 22:35 ` [PATCH 15/22] linux-user, x86_64: " Laurent Vivier
2020-02-17 22:35 ` [PATCH 16/22] linux-user,mips: " Laurent Vivier
2020-02-18 17:54   ` [PATCH 16/22] linux-user, mips: " Aleksandar Markovic
2020-02-17 22:35 ` [PATCH 17/22] linux-user,mips64: split syscall_nr.h Laurent Vivier
2020-02-18 17:54   ` Aleksandar Markovic
2020-02-17 22:35 ` [PATCH 18/22] linux-user, mips64: add syscall table generation support Laurent Vivier
2020-02-18 17:55   ` Aleksandar Markovic
2020-02-17 22:35 ` [PATCH 19/22] linux-user,scripts: add a script to update syscall.tbl Laurent Vivier
2020-02-18 17:56   ` [PATCH 19/22] linux-user, scripts: " Aleksandar Markovic
2020-02-17 22:35 ` [PATCH 20/22] linux-user: update syscall.tbl from linux 0bf999f9c5e7 Laurent Vivier
2020-02-18 11:54   ` Aleksandar Markovic
2020-02-18 17:57   ` Aleksandar Markovic
2020-02-17 22:35 ` [PATCH 21/22] linux-user,mips: move content of mips_syscall_args Laurent Vivier
2020-02-18 17:58   ` Aleksandar Markovic
2020-02-19 18:58     ` Aleksandar Markovic
2020-02-19 19:39       ` Laurent Vivier
2020-02-19 20:02         ` Aleksandar Markovic
2020-02-17 22:35 ` [PATCH 22/22] linux-user,mips: update syscall-args-o32.c.inc Laurent Vivier
2020-02-18 17:58   ` Aleksandar Markovic
2020-02-18  6:13 ` [PATCH 00/22] linux-user: generate syscall_nr.sh Philippe Mathieu-Daudé
2020-02-18  8:36   ` Laurent Vivier
2020-02-18 11:51     ` Aleksandar Markovic
2020-02-18 13:00       ` Philippe Mathieu-Daudé
2020-02-18 14:27 ` Cornelia Huck
2020-02-18 15:19   ` Laurent Vivier
2020-02-18 17:15     ` Cornelia Huck
2020-02-18 17:46       ` Aleksandar Markovic
2020-02-18 17:56         ` Cornelia Huck [this message]
2020-02-18 22:48 ` Alistair Francis
2020-02-19  8:29   ` Laurent Vivier

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20200218185638.7a626b30.cohuck@redhat.com \
    --to=cohuck@redhat.com \
    --cc=aleksandar.m.mail@gmail.com \
    --cc=aleksandar.rikalo@rt-rk.com \
    --cc=amarkovic@wavecomp.com \
    --cc=aurelien@aurel32.net \
    --cc=laurent@vivier.eu \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-s390x@nongnu.org \
    --cc=riku.voipio@iki.fi \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).