From: Palmer Dabbelt <palmer@rivosinc.com>
To: jeffreyalaw@gmail.com
Cc: Vineet Gupta <vineetg@rivosinc.com>,
kito.cheng@sifive.com, Robin Dapp <rdapp.gcc@gmail.com>,
gcc-patches@gcc.gnu.org
Subject: Re: RISC-V patchworks call tomorrow ?
Date: Mon, 06 Nov 2023 23:21:56 -0800 (PST) [thread overview]
Message-ID: <mhng-e2bf9ede-e1b1-4454-92c1-3f728b98b9ee@palmer-ri-x1c9a> (raw)
In-Reply-To: <446b5f14-baff-409b-9c6e-c04e7170cf1d@gmail.com>
On Mon, 06 Nov 2023 18:47:24 PST (-0800), jeffreyalaw@gmail.com wrote:
>
>
> On 11/6/23 18:19, Vineet Gupta wrote:
>> Do we have call tomorrow, given some folks are traveling for RV Summit ?
> I'll be in the air, so "no" from me.
I'll be on the ground, but not sure that counts for much. IIRC Kito
isn't going to the summit, so he should be as awake as he ever is (IIRC
it's around midnight there).
So sounds like you might need to hit the 10 minute rule yourself?
prev parent reply other threads:[~2023-11-07 7:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-07 1:19 Vineet Gupta
2023-11-07 2:47 ` Jeff Law
2023-11-07 7:21 ` Palmer Dabbelt [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=mhng-e2bf9ede-e1b1-4454-92c1-3f728b98b9ee@palmer-ri-x1c9a \
--to=palmer@rivosinc.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jeffreyalaw@gmail.com \
--cc=kito.cheng@sifive.com \
--cc=rdapp.gcc@gmail.com \
--cc=vineetg@rivosinc.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 read-only IMAP folder(s) and NNTP newsgroup(s).