linux-perf-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Howard Chu <howardchu95@gmail.com>
Cc: Ian Rogers <irogers@google.com>,
	linux-perf-users <linux-perf-users@vger.kernel.org>,
	Namhyung Kim <namhyung@kernel.org>
Subject: Re: Linux Perf Tool Office Hours
Date: Thu, 20 Jun 2024 12:50:58 -0300	[thread overview]
Message-ID: <ZnRP4hJLcRpZzs4x@x1> (raw)
In-Reply-To: <CAH0uvoiCX=asogf6e4D8mZ2Yw+8pj3HMTyvYTtQjFTtgKKP6GQ@mail.gmail.com>

On Thu, Jun 20, 2024 at 11:40:44PM +0800, Howard Chu wrote:
> Hi,
> 
> Ian is busy so I'll do the announcement.
> 
> 4th week of Google Summer-of-Code. Office hours this week are the same
> as last week:

Great, I'll be there.

- Arnaldo
 
> Linux perf tool office hours
> Friday, June 21 · 8:00 – 9:00am
> 
> To join the office hours, use the link below:
> 
> Time zone: America/Los_Angeles
> Google Meet joining info
> Video call link: https://meet.google.com/tif-efem-uiq
> Or dial: ‪(US) +1 425-217-5482‬ PIN: ‪791 261 968‬#
> More phone numbers: https://tel.meet/tif-efem-uiq?pin=2651187837256
> 
> Thanks,
> Howard
> 
> On Thu, Jun 13, 2024 at 9:48 PM Ian Rogers <irogers@google.com> wrote:
> >
> > Hi,
> >
> > 3rd week of Google Summer-of-Code. Office hours this week are the same
> > as last week:
> >
> > Linux perf tool office hours
> > Friday, June 14 · 8:00 – 9:00am
> > Time zone: America/Los_Angeles
> > Google Meet joining info
> > Video call link: https://meet.google.com/tif-efem-uiq
> > Or dial: ‪(US) +1 425-217-5482‬ PIN: ‪791 261 968‬#
> > More phone numbers: https://tel.meet/tif-efem-uiq?pin=2651187837256
> >
> > Thanks,
> > Ian

  reply	other threads:[~2024-06-20 15:51 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-29  1:01 Linux Perf Tool Office Hours Ian Rogers
2024-06-05  0:11 ` Ian Rogers
2024-06-13 13:48   ` Ian Rogers
2024-06-20 15:40     ` Howard Chu
2024-06-20 15:50       ` Arnaldo Carvalho de Melo [this message]
2024-06-27 17:48         ` Ian Rogers
2024-07-04  2:41           ` Howard Chu
2024-07-11 16:25             ` Ian Rogers
2024-07-18 21:32               ` Ian Rogers
2024-07-25 20:56                 ` Ian Rogers
2024-08-01 20:15                   ` Ian Rogers
2024-08-08 18:25                     ` Ian Rogers
2024-08-16  0:00                       ` Ian Rogers
2024-08-22 17:43                         ` Ian Rogers
  -- strict thread matches above, loose matches on Subject: below --
2023-05-31 17:00 Ian Rogers
2023-06-08  4:14 ` Ian Rogers
2023-06-14 17:01   ` Ian Rogers
2023-06-21 22:15     ` Ian Rogers
2023-07-06 15:31       ` Ian Rogers
2023-07-12 22:42         ` Ian Rogers
2023-07-19 22:29           ` Ian Rogers
2023-07-26 21:53             ` Ian Rogers
2023-08-02 20:09               ` Ian Rogers
2023-08-09 20:32                 ` Ian Rogers
2023-08-17  6:16                   ` Ian Rogers
2023-08-24  4:41                     ` Ian Rogers
2023-08-31  6:33                       ` Ian Rogers
2022-05-01 18:11 Ian Rogers
2022-05-02 16:35 ` Tanusree Debnath
2022-05-05 16:57   ` Ian Rogers
2022-05-12 16:34     ` Ian Rogers
2022-05-15 23:37       ` Ian Rogers
2022-05-18 16:17         ` Ian Rogers
2022-05-19 13:04           ` Ian Rogers

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=ZnRP4hJLcRpZzs4x@x1 \
    --to=acme@kernel.org \
    --cc=howardchu95@gmail.com \
    --cc=irogers@google.com \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=namhyung@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;
as well as URLs for NNTP newsgroup(s).