From: Alasdair G Kergon <agk@redhat.com>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Alasdair Kergon <agk@redhat.com>,
Mike Snitzer <snitzer@redhat.com>,
dm-devel@redhat.com
Subject: Re: linux-next: Tree for Nov 15 (drivers/md/dm-integrity)
Date: Mon, 18 Nov 2019 16:32:18 +0000 [thread overview]
Message-ID: <20191118163218.GF1800@agk-dp.fab.redhat.com> (raw)
In-Reply-To: <d3a96436-0d9c-a13f-7524-33b203910367@infradead.org>
On Fri, Nov 15, 2019 at 08:19:53AM -0800, Randy Dunlap wrote:
> BTW, dm-devel@redhat.com seems to be invalid or dead.
Red Hat made a few changes to its mail configuration over the last
week.
If anyone reading this still has problems that might be related to
this, please send me the relevant details privately (e.g. full headers
of messages) and I'll try to engage the right people to help.
Alasdair
next prev parent reply other threads:[~2019-11-18 16:32 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-15 8:05 linux-next: Tree for Nov 15 Stephen Rothwell
2019-11-15 16:02 ` linux-next: Tree for Nov 15 (objtool) Randy Dunlap
2019-11-15 16:38 ` Josh Poimboeuf
2020-01-20 15:37 ` Josh Poimboeuf
2019-11-15 16:11 ` linux-next: Tree for Nov 15 Naresh Kamboju
2019-11-15 16:17 ` linux-next: Tree for Nov 15 (drivers/md/dm-integrity) Randy Dunlap
2019-11-15 16:19 ` Randy Dunlap
2019-11-15 19:27 ` Mike Snitzer
2019-11-18 16:32 ` Alasdair G Kergon [this message]
2019-11-15 22:46 ` Stephen Rothwell
2019-11-15 23:10 ` Mike Snitzer
2019-11-15 23:32 ` Stephen Rothwell
2019-11-15 16:35 ` linux-next: Tree for Nov 15 (sound/soc/codecs/rt5677) Randy Dunlap
2019-11-15 23:44 ` linux-next: Tree for Nov 15 (thermal: THERMAL_GOV_POWER_ALLOCATOR) Randy Dunlap
2019-12-04 16:25 ` Randy Dunlap
2019-12-05 4:27 ` Zhang Rui
2019-12-05 4:36 ` Quentin Perret
2019-12-05 5:50 ` Zhang Rui
2019-12-05 5:47 ` Randy Dunlap
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=20191118163218.GF1800@agk-dp.fab.redhat.com \
--to=agk@redhat.com \
--cc=dm-devel@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=sfr@canb.auug.org.au \
--cc=snitzer@redhat.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).