Linux PCI subsystem development
 help / color / mirror / Atom feed
From: Ira Weiny <ira.weiny@intel.com>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Cc: Davidlohr Bueso <dave@stgolabs.net>,
	Dan Williams <dan.j.williams@intel.com>,
	Jonathan Cameron <Jonathan.Cameron@huawei.com>,
	Bjorn Helgaas <bhelgaas@google.com>,
	Lukas Wunner <lukas@wunner.de>, <linux-pci@vger.kernel.org>,
	<linux-acpi@vger.kernel.org>, Bjorn Helgaas <helgaas@kernel.org>
Subject: Re: [PATCH v4 0/9] CXL: Process event logs
Date: Mon, 12 Dec 2022 10:46:26 -0800	[thread overview]
Message-ID: <Y5d3ArpuLYl4g4Mc@iweiny-desk3> (raw)
In-Reply-To: <20221212161613.mz42m7n6eswjwdjv@meerkat.local>

On Mon, Dec 12, 2022 at 11:16:13AM -0500, Konstantin Ryabitsev wrote:
> On Sun, Dec 11, 2022 at 09:32:33PM -0800, Ira Weiny wrote:
> > My apologies.  Please ignore this series.
> > 
> > I'm trying to use the new b4 send functionality and was trying to send this
> > only to myself.  I'm not sure what went wrong.  The patches should be ok but
> > this did not get sent to all the intended lists and people.
> > 
> > I'm going to resend this hopefully to all the right addresses this time.
> 
> Ira:

First off thanks for the quick response and I have to say b4 send looks like an
awesome tool.  So I hope the above was not taken the wrong way.

> 
> I don't think anything went wrong -- you probably used the new "reflect"
> feature, right?

I did!  :-D

> It fills out the To: and Cc: headers but doesn't actually send
> actual mail to those accounts. Mail servers don't actually pay any attention
> to those headers -- all that matters is what destinations are given to the
> server during the envelope negotiation.

I did not know that.  But I was kind of coming to that conclusion based on
what I saw happen.

> 
> I do realize that this is confusing. :/

Only to those mere mortals such as myself who don't know squat about mail
protocols!  :-D

> 
> Should I include anything in the output about this?

Maybe.  I'm not trying to put more burden on you.  But for the ignorant maybe
it is a good idea.  I did panic when I saw all the to/cc addresses filled in.

FWIW I do like the idea of seeing the headers as they appear.  My personal
scripts have features to dump emails before trying to send.  So now that I know
what happened I kind of like it.

Thanks,
Ira

  reply	other threads:[~2022-12-12 18:48 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20221211-test-b4-v4-0-9f45dfeec102@intel.com>
2022-12-12  5:32 ` [PATCH v4 0/9] CXL: Process event logs Ira Weiny
2022-12-12 16:16   ` Konstantin Ryabitsev
2022-12-12 18:46     ` Ira Weiny [this message]
2022-12-12 18:54       ` Konstantin Ryabitsev
2022-12-12 21:24         ` Ira Weiny
2022-12-12  7:06 [PATCH V4 " ira.weiny
2022-12-16 12:25 ` Jonathan Cameron
2022-12-16 17:01   ` Dan Williams
2022-12-16 18:15     ` Ira Weiny
2022-12-16 18:39     ` Jonathan Cameron

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=Y5d3ArpuLYl4g4Mc@iweiny-desk3 \
    --to=ira.weiny@intel.com \
    --cc=Jonathan.Cameron@huawei.com \
    --cc=bhelgaas@google.com \
    --cc=dan.j.williams@intel.com \
    --cc=dave@stgolabs.net \
    --cc=helgaas@kernel.org \
    --cc=konstantin@linuxfoundation.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=lukas@wunner.de \
    /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