From: delyan@sonic.net
To: devicetree-spec+unsubscribe@vger.kernel.org,
devicetree-spec@vger.kernel.org,
dmaengine+subscribe@vger.kernel.org,
dmaengine+unsubscribe@vger.kernel.org, dmaengine@vger.kernel.org,
dwarves+subscribe@vger.kernel.org,
dwarves+unsubscribe@vger.kernel.org, dwarves@vger.kernel.org,
ecryptfs+subscribe@vger.kernel.org,
ecryptfs+unsubscribe@vger.kernel.org, ecryptfs@vger.kernel.org,
fio+subscribe@vger.kernel.org, fio+unsubscribe@vger.kernel.org,
fio@vger.kernel.org, fstests+subscribe@vger.kernel.org
Subject: subscribe
Date: Tue, 27 Feb 2024 01:52:18 -0500 [thread overview]
Message-ID: <65DD86A2.17414.445FAC2F@delyan.sonic.net> (raw)
subscribe
reply other threads:[~2024-02-27 6:52 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=65DD86A2.17414.445FAC2F@delyan.sonic.net \
--to=delyan@sonic.net \
--cc=devicetree-spec+unsubscribe@vger.kernel.org \
--cc=devicetree-spec@vger.kernel.org \
--cc=dmaengine+subscribe@vger.kernel.org \
--cc=dmaengine+unsubscribe@vger.kernel.org \
--cc=dmaengine@vger.kernel.org \
--cc=dwarves+subscribe@vger.kernel.org \
--cc=dwarves+unsubscribe@vger.kernel.org \
--cc=dwarves@vger.kernel.org \
--cc=ecryptfs+subscribe@vger.kernel.org \
--cc=ecryptfs+unsubscribe@vger.kernel.org \
--cc=ecryptfs@vger.kernel.org \
--cc=fio+subscribe@vger.kernel.org \
--cc=fio+unsubscribe@vger.kernel.org \
--cc=fio@vger.kernel.org \
--cc=fstests+subscribe@vger.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 read-only IMAP folder(s) and NNTP newsgroup(s).