From: Peter Maydell <peter.maydell@linaro.org>
To: Patrick Venture <venture@google.com>
Cc: "Hao Wu" <wuhaotsh@google.com>,
"Corey Minyard" <cminyard@mvista.com>,
"Philippe Mathieu-Daudé" <f4bug@amsat.org>,
"QEMU Developers" <qemu-devel@nongnu.org>
Subject: Re: [PATCH] hw/i2c: flatten pca954x mux device
Date: Wed, 2 Feb 2022 19:01:23 +0000 [thread overview]
Message-ID: <CAFEAcA-N3BwSNsXSidXK6PgmjDrGfOQabyfVRv03nnyLpsBURw@mail.gmail.com> (raw)
In-Reply-To: <CAO=notzLfum_zkXhP+xQ9RTxcpG3oNxwFMPYWz+o1vYdF8ynQg@mail.gmail.com>
On Wed, 2 Feb 2022 at 17:36, Patrick Venture <venture@google.com> wrote:
> Just saw your reply, and found a bunch of other non-spam in my
> spam folder. I sent the message to the anti-spam team, hopefully
> that'll resolve this for myself and presumably others.
I dunno if you folk get a specially tuned version or just
the standard gmail spam filter, but IME it's not very good
with mailing list traffic. In particular "this is a patch"
should be a really really easy thing to detect as not-spam
but it doesn't always manage it. I have my filters set to
"Do not send to spam" for mailing list traffic...
-- PMM
next prev parent reply other threads:[~2022-02-02 19:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-01 16:30 [PATCH] hw/i2c: flatten pca954x mux device Patrick Venture
2022-02-01 19:02 ` Philippe Mathieu-Daudé via
2022-02-01 20:54 ` Patrick Venture
2022-02-02 16:20 ` Philippe Mathieu-Daudé via
2022-02-02 16:34 ` Patrick Venture
2022-02-02 16:40 ` Patrick Venture
2022-02-02 17:30 ` Philippe Mathieu-Daudé via
2022-02-02 21:30 ` Patrick Venture
2022-02-02 19:01 ` Peter Maydell [this message]
2022-02-02 19:53 ` Patrick Venture
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=CAFEAcA-N3BwSNsXSidXK6PgmjDrGfOQabyfVRv03nnyLpsBURw@mail.gmail.com \
--to=peter.maydell@linaro.org \
--cc=cminyard@mvista.com \
--cc=f4bug@amsat.org \
--cc=qemu-devel@nongnu.org \
--cc=venture@google.com \
--cc=wuhaotsh@google.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 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.