From: Jonathan Cameron <Jonathan.Cameron@Huawei.com>
To: "Luck, Tony" <tony.luck@intel.com>
Cc: Peter Newman <peternewman@google.com>,
Drew Fustini <dfustini@baylibre.com>,
"babu.moger@amd.com" <babu.moger@amd.com>,
"Chatre, Reinette" <reinette.chatre@intel.com>,
"james.morse@arm.com" <james.morse@arm.com>,
Amit Singh Tomar <amitsinght@marvell.com>,
"Yu, Fenghua" <fenghua.yu@intel.com>,
George Cherian <gcherian@marvell.com>,
"robh@kernel.org" <robh@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
Jon Masters <jonmasters@google.com>,
"Eranian, Stephane" <eranian@google.com>
Subject: Re: resctrl2 - status
Date: Fri, 29 Sep 2023 10:38:59 +0100 [thread overview]
Message-ID: <20230929103859.00002d3f@Huawei.com> (raw)
In-Reply-To: <SJ1PR11MB6083C7959787B9816D951E0FFCC1A@SJ1PR11MB6083.namprd11.prod.outlook.com>
On Thu, 28 Sep 2023 14:47:13 +0000
"Luck, Tony" <tony.luck@intel.com> wrote:
> > I got us a BoF session to talk about resctrl and porting it to new
> > architectures:
>
> Thanks for doing this.
Great!
>
> > https://lpc.events/event/17/contributions/1567/
> >
> > To anyone planning to attend, while the schedule is still easy to
> > adjust, please let me know if the proposed time (Nov 15, 4:30-5:15pm)
> > doesn't work.
>
> Do you know if the BoF sessions are going to be remote accessible?
> Personal conflicts mean I can't attend in person.
They were last year (it worked surprisingly well). If there are any problems
we can set up a jabra in the room.
I'm keen to attend this. That time currently works for me though I got
the impression things are still very fluid on schedule (I sent a list
of uconfs to avoid for the PCI device attestation BoF that is just before
this in the posted schedule.)
So if there are obvious clashes to avoid, (I can't immediately spot any
general ones) then pass those on.
Jonathan
>
> -Tony
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2023-09-29 9:39 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-24 18:10 resctrl2 - status Luck, Tony
2023-08-25 17:47 ` Reinette Chatre
2023-08-25 18:09 ` Luck, Tony
2023-08-25 18:58 ` Reinette Chatre
2023-08-25 19:44 ` Luck, Tony
2023-08-25 20:20 ` Reinette Chatre
2023-08-25 20:54 ` Tony Luck
2023-08-25 23:08 ` Reinette Chatre
2023-08-26 1:11 ` Tony Luck
2023-08-28 14:50 ` Reinette Chatre
2023-09-06 18:21 ` Tony Luck
2023-09-08 18:08 ` Moger, Babu
2023-09-08 18:51 ` Luck, Tony
2023-09-08 21:35 ` Moger, Babu
2023-09-08 23:13 ` Tony Luck
2023-09-15 17:55 ` Drew Fustini
2023-09-18 10:44 ` Jonathan Cameron
2023-09-28 8:47 ` Peter Newman
2023-09-28 14:47 ` Luck, Tony
2023-09-29 9:38 ` Jonathan Cameron [this message]
2023-09-29 14:49 ` Drew Fustini
2023-09-15 17:16 ` James Morse
2023-09-15 20:38 ` Tony Luck
2023-09-21 0:21 ` Tony Luck
2023-09-19 12:53 ` Peter Newman
2023-09-19 16:40 ` Tony Luck
2023-08-29 10:23 ` Jonathan Cameron
2023-08-29 17:18 ` [EXT] " Amit Singh Tomar
2023-08-30 10:47 ` Jonathan Cameron
2023-09-15 17:16 ` James Morse
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=20230929103859.00002d3f@Huawei.com \
--to=jonathan.cameron@huawei.com \
--cc=amitsinght@marvell.com \
--cc=babu.moger@amd.com \
--cc=dfustini@baylibre.com \
--cc=eranian@google.com \
--cc=fenghua.yu@intel.com \
--cc=gcherian@marvell.com \
--cc=james.morse@arm.com \
--cc=jonmasters@google.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peternewman@google.com \
--cc=reinette.chatre@intel.com \
--cc=robh@kernel.org \
--cc=tony.luck@intel.com \
/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).