All of lore.kernel.org
 help / color / mirror / Atom feed
From: SeongJae Park <sj@kernel.org>
To: SeongJae Park <sj@kernel.org>
Cc: damon@lists.linux.dev, linux-damon@amazon.com,
	linux-damon-trial@amazon.com, linux-mm@kvack.org,
	linux-kernel@vger.kernel.org
Subject: Re: DAMON Beer/Coffee/Tea chat series
Date: Tue, 30 Aug 2022 21:54:28 +0000	[thread overview]
Message-ID: <20220830215428.84567-1-sj@kernel.org> (raw)
In-Reply-To: <20220810225102.124459-1-sj@kernel.org>

Hello,

On Wed, 10 Aug 2022 22:51:02 +0000 SeongJae Park <sj@kernel.org> wrote:

> Hello,
> 
> 
> In short, I'd like to start an open, regular, and informal virtual bi-weekly
> meeting series for DAMON community.
> 
> Important links and dates
> -------------------------
> 
> Location: https://meet.google.com/ndx-evoc-gbu
> Agenda: https://docs.google.com/document/d/1v43Kcj3ly4CYqmAkMaZzLiM2GEnWfgdGbZAH3mi2vpM/edit?usp=sharing
> 
> First instance: 2022-08-15 18:00 PDT
> Second instance: 2022-08-30 09:00 PDT

According to the bi-weekly schedule, the third instance of this meeting series
should be scheduled to 2022-09-12 18:00 PDT.  It means it will conflict with
LPC'22[1].  For the reason, I'd like to reserve a session in the BoF trakc of
the conference, and do an _in-persion_ DAMON community meeting in the session.
The session could also include some followup QnA/discussions of the kernel
summit DAMON talk[2].

I just submitted the BoF proposal asking it to be scheduled after the kernel
summit DAMON talk.  I will provide further update once I get the feedback from
the committee.  Hope it to be accepted!

[1] https://lpc.events/
[2] https://lpc.events/event/16/contributions/1224/


Thanks,
SJ

[...]

  parent reply	other threads:[~2022-08-30 21:54 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-10 22:51 DAMON Beer/Coffee/Tea chat series SeongJae Park
2022-08-29 20:15 ` SeongJae Park
2022-08-30 21:54 ` SeongJae Park [this message]
2022-09-09 17:38   ` SeongJae Park
2022-09-19 22:14     ` SeongJae Park
2023-11-08 14:55     ` SeongJae Park
2022-09-28 17:59 ` SeongJae Park
2022-10-18 16:59 ` SeongJae Park
2022-11-01  1:33 ` SeongJae Park
2022-11-14 16:51 ` SeongJae Park
2022-11-28 17:21 ` SeongJae Park
2022-12-13  1:52 ` SeongJae Park
2023-01-24  1:44 ` SeongJae Park
2023-01-24 23:06   ` SeongJae Park
2023-04-21 19:45 ` SeongJae Park
2023-05-18 18:53 ` SeongJae Park
2023-08-01  1:21 ` SeongJae Park
2023-08-01  1:27   ` SeongJae Park
2023-12-20 20:27 ` SeongJae Park
2024-01-03 20:30   ` SeongJae Park
2024-01-16 18:09 ` SeongJae Park
2024-04-09 23:05 ` SeongJae Park
2024-04-16 18:40 ` Third in-person DAMON Beer/Coffee/Tea chat SeongJae Park
2024-05-19 16:33 ` DAMON Beer/Coffee/Tea chat reminder and extending for office hour SeongJae Park
2024-05-31 22:42   ` SeongJae Park
2024-06-14 21:19   ` SeongJae Park
2024-06-30 17:09   ` SeongJae Park
2024-07-17 23:58   ` Shared calendar for the schedule (was Re: DAMON Beer/Coffee/Tea chat reminder and extending for office hour) SeongJae Park
2024-07-26  0:37   ` DAMON Beer/Coffee/Tea chat reminder (was: " SeongJae Park
2024-08-09 17:21   ` SeongJae Park
2024-08-23  0:21   ` SeongJae Park
2024-08-30 22:52   ` SeongJae Park

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=20220830215428.84567-1-sj@kernel.org \
    --to=sj@kernel.org \
    --cc=damon@lists.linux.dev \
    --cc=linux-damon-trial@amazon.com \
    --cc=linux-damon@amazon.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.