From: Thomas Gleixner <tglx@linutronix.de>
To: Mauro Carvalho Chehab <mchehab+samsung@kernel.org>
Cc: James Bottomley <James.Bottomley@HansenPartnership.com>,
ksummit-discuss@lists.linuxfoundation.org
Subject: Re: [Ksummit-discuss] [MAINTAINER TOPIC] Succession Planning: Is It time to Throw Linus Under a Bus?
Date: Sat, 8 Sep 2018 12:50:37 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.21.1809081250020.1402@nanos.tec.linutronix.de> (raw)
In-Reply-To: <20180908074708.249571f4@coco.lan>
On Sat, 8 Sep 2018, Mauro Carvalho Chehab wrote:
> Also, if we want to consider the bus scenario and other disaster
> threats, it could be worth to consider having them geographically
> distributed (if possible even on different Countries).
And consequently forbid them to ever meet at the same place ....
next prev parent reply other threads:[~2018-09-08 10:50 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-06 19:44 James Bottomley
2018-09-06 19:47 ` Daniel Vetter
2018-09-06 19:51 ` James Bottomley
2018-09-06 20:06 ` Geert Uytterhoeven
2018-09-06 20:35 ` Olof Johansson
2018-09-06 20:45 ` Linus Torvalds
2018-09-06 20:52 ` Olof Johansson
2018-09-08 10:47 ` Mauro Carvalho Chehab
2018-09-08 10:50 ` Thomas Gleixner [this message]
2018-09-08 12:21 ` Daniel Vetter
2018-09-09 13:56 ` Laurent Pinchart
2018-09-09 20:05 ` Jiri Kosina
2018-09-06 19:57 ` Linus Torvalds
2018-09-06 20:51 ` James Bottomley
2018-09-06 20:59 ` Linus Torvalds
2018-09-06 21:13 ` James Bottomley
2018-09-06 21:20 ` Jens Axboe
2018-09-06 21:28 ` John W. Linville
2018-09-06 21:34 ` Jens Axboe
2018-09-06 21:41 ` Linus Torvalds
2018-09-06 22:12 ` David Woodhouse
2018-09-06 22:19 ` Linus Torvalds
2018-09-06 22:29 ` James Bottomley
2018-09-06 21:37 ` Olof Johansson
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=alpine.DEB.2.21.1809081250020.1402@nanos.tec.linutronix.de \
--to=tglx@linutronix.de \
--cc=James.Bottomley@HansenPartnership.com \
--cc=ksummit-discuss@lists.linuxfoundation.org \
--cc=mchehab+samsung@kernel.org \
/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