From: Vlastimil Babka <vbabka@suse.cz>
To: Greg KH <greg@kroah.com>, Jani Nikula <jani.nikula@intel.com>
Cc: "Bird, Tim" <Tim.Bird@sony.com>,
"ksummit-discuss@lists.linuxfoundation.org"
<ksummit-discuss@lists.linuxfoundation.org>,
"tech-board-discuss@lists.linuxfoundation.org"
<tech-board-discuss@lists.linuxfoundation.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [Ksummit-discuss] [Tech-board-discuss] Linux Foundation Technical Advisory Board Elections -- Change to charter
Date: Fri, 13 Mar 2020 10:41:57 +0100 [thread overview]
Message-ID: <24c64c56-947b-4267-33b8-49a22f719c81@suse.cz> (raw)
In-Reply-To: <20200313093548.GA2089143@kroah.com>
On 3/13/20 10:35 AM, Greg KH wrote:
>> Not that I'm saying there's an easy solution, but obviously kernel.org
>> account is not as problem free as you might think.
>
> We are not saying it is "problem free", but what really is the problem
> with it?
IIUC there is no problem for its current use, but it would be rather restrictive
if it was used as the only criterion for being able to vote for TAB remotely.
> thanks,
>
> greg k-h
> _______________________________________________
> Ksummit-discuss mailing list
> Ksummit-discuss@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/ksummit-discuss
>
_______________________________________________
Ksummit-discuss mailing list
Ksummit-discuss@lists.linuxfoundation.org
https://lists.linuxfoundation.org/mailman/listinfo/ksummit-discuss
next prev parent reply other threads:[~2020-03-13 9:42 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-12 0:19 [Ksummit-discuss] Linux Foundation Technical Advisory Board Elections -- Change to charter Laura Abbott
2020-03-12 0:34 ` Laurent Pinchart
2020-03-12 2:20 ` Laura Abbott
2020-03-12 21:28 ` Bird, Tim
2020-03-12 22:58 ` Laura Abbott
2020-03-13 3:19 ` Theodore Y. Ts'o
2020-03-13 8:58 ` Jani Nikula
2020-03-13 9:35 ` [Ksummit-discuss] [Tech-board-discuss] " Greg KH
2020-03-13 9:41 ` Vlastimil Babka [this message]
2020-03-13 10:07 ` Greg KH
2020-03-13 10:16 ` Geert Uytterhoeven
2020-03-13 10:37 ` Greg KH
2020-03-13 10:50 ` Geert Uytterhoeven
2020-03-13 12:12 ` Steven Rostedt
2020-03-13 14:10 ` Jani Nikula
2020-03-13 14:52 ` Theodore Y. Ts'o
2020-03-13 15:08 ` Jani Nikula
2020-03-13 15:26 ` James Bottomley
2020-03-13 17:14 ` Bird, Tim
2020-03-13 17:36 ` Steven Rostedt
2020-03-13 15:18 ` James Bottomley
2020-03-13 10:30 ` Jani Nikula
2020-03-13 13:05 ` Sasha Levin
2020-03-13 15:42 ` Steven Rostedt
2020-03-13 14:59 ` Konstantin Ryabitsev
2020-03-13 15:07 ` Jani Nikula
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=24c64c56-947b-4267-33b8-49a22f719c81@suse.cz \
--to=vbabka@suse.cz \
--cc=Tim.Bird@sony.com \
--cc=greg@kroah.com \
--cc=jani.nikula@intel.com \
--cc=ksummit-discuss@lists.linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tech-board-discuss@lists.linuxfoundation.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;
as well as URLs for NNTP newsgroup(s).