From: Bjorn Helgaas <helgaas@kernel.org>
To: Sui Jingfeng <15330273260@189.cn>
Cc: Bjorn Helgaas <bhelgaas@google.com>,
Matthew Wilcox <willy@infradead.org>,
Ben Hutchings <bhutchings@solarflare.com>,
Jesse Barnes <jbarnes@virtuousgeek.org>,
kernel test robot <lkp@intel.com>, Li Yi <liyi@loongson.cn>,
linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
loongson-kernel@lists.loongnix.cn,
Geert Uytterhoeven <geert@linux-m68k.org>,
linux-pci@vger.kernel.org
Subject: Re: [PATCH v2] PCI: Add dummy implement for pci_clear_master() function
Date: Wed, 31 May 2023 13:03:09 -0500 [thread overview]
Message-ID: <ZHeL3WsalhsIMYwa@bhelgaas> (raw)
In-Reply-To: <47c5c3ca-b112-9800-a047-10dab4cdef50@189.cn>
On Thu, Jun 01, 2023 at 01:44:52AM +0800, Sui Jingfeng wrote:
> Can you receive my email?
>
> I reply several email to you, but Thunderbird told me that may mail is
> returned.
>
> Maybe you could read the content at lore.
I do receive your email (at least some; obviously if there are things
I don't receive I wouldn't know). I read most Linux email via lei [1],
so if it shows up on lore, I should see it.
Bjorn
[1] https://people.kernel.org/monsieuricon/lore-lei-part-1-getting-started
next prev parent reply other threads:[~2023-05-31 18:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-31 10:27 [PATCH v2] PCI: Add dummy implement for pci_clear_master() function Sui Jingfeng
2023-05-31 10:27 ` Sui Jingfeng
2023-05-31 17:28 ` Bjorn Helgaas
2023-05-31 17:44 ` Sui Jingfeng
2023-05-31 18:03 ` Bjorn Helgaas [this message]
2023-06-20 4:04 ` Sui Jingfeng
2023-06-20 11:06 ` Bjorn Helgaas
2023-06-20 11:06 ` Bjorn Helgaas
2023-06-20 11:37 ` Sui Jingfeng
2023-06-20 11:37 ` Sui Jingfeng
2023-06-20 11:52 ` Bjorn Helgaas
2023-06-20 11:52 ` Bjorn Helgaas
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=ZHeL3WsalhsIMYwa@bhelgaas \
--to=helgaas@kernel.org \
--cc=15330273260@189.cn \
--cc=bhelgaas@google.com \
--cc=bhutchings@solarflare.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=geert@linux-m68k.org \
--cc=jbarnes@virtuousgeek.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=liyi@loongson.cn \
--cc=lkp@intel.com \
--cc=loongson-kernel@lists.loongnix.cn \
--cc=willy@infradead.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 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.