From: Ed Tanous <edtanous@google.com>
To: Andrew Jeffery <andrew@aj.id.au>
Cc: openbmc <openbmc@lists.ozlabs.org>, Joseph Reynolds <jrey@linux.ibm.com>
Subject: Re: Security Working Group - Wednesday May 26 - results
Date: Wed, 2 Jun 2021 08:19:23 -0700 [thread overview]
Message-ID: <CAH2-KxDTVo9oB_r0w=CSMatt0Pniq-pp4=Ps9Gs8LA04mdBafA@mail.gmail.com> (raw)
In-Reply-To: <84217f2a-8351-48e9-964c-de34f4496c67@www.fastmail.com>
On Thu, May 27, 2021 at 8:10 PM Andrew Jeffery <andrew@aj.id.au> wrote:
>
>
>
> On Fri, 28 May 2021, at 00:34, Joseph Reynolds wrote:
> > On 5/27/21 7:56 AM, Patrick Williams wrote:
> > > On Wed, May 26, 2021 at 01:59:57PM -0500, Joseph Reynolds wrote:
> > >> On 5/26/21 8:43 AM, Joseph Reynolds wrote:
> > >
> > >>> 1. Followup from last meeting re uboot, kexec, sysrq-trigger on ARM
> > >>> architecture.
> > >> We re-hashed the discussion, added new information, and added new concerns.
> > > Could you paste the minutes here when you reply to these? It is kind of
> > > hard to have any discussion with the rest of the community when you have
> > > 2-3 levels of indirection to get at the words.
> >
> > Thanks for your email!
> >
> > Yes, I've waffled between cut/paste of the minutes and summarizing
> > them. I prefer to cut/paste, so I'll do that consistently from now on.
>
> +1, it makes it much easier for people who can't attend to provide input.
>
> The other thing I'd like to see is attendance / attribution of
> comments, that way I know who I need discuss particular items with.
+1
>
> Cheers,
>
> Andrew
prev parent reply other threads:[~2021-06-02 15:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-26 13:43 Security Working Group - Wednesday May 26 Joseph Reynolds
2021-05-26 18:59 ` Security Working Group - Wednesday May 26 - results Joseph Reynolds
2021-05-27 12:56 ` Patrick Williams
2021-05-27 15:04 ` Joseph Reynolds
2021-05-28 3:09 ` Andrew Jeffery
2021-06-02 15:19 ` Ed Tanous [this message]
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='CAH2-KxDTVo9oB_r0w=CSMatt0Pniq-pp4=Ps9Gs8LA04mdBafA@mail.gmail.com' \
--to=edtanous@google.com \
--cc=andrew@aj.id.au \
--cc=jrey@linux.ibm.com \
--cc=openbmc@lists.ozlabs.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).