public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Joerg Roedel <joro@8bytes.org>
To: Chunyan Zhang <zhang.lyra@gmail.com>
Cc: Will Deacon <will@kernel.org>,
	Robin Murphy <robin.murphy@arm.com>,
	iommu@lists.linux.dev, Baolu Lu <baolu.lu@linux.intel.com>,
	Baolin Wang <baolin.wang@linux.alibaba.com>,
	Orson Zhai <orsonzhai@gmail.com>,
	LKML <linux-kernel@vger.kernel.org>,
	Chunyan Zhang <chunyan.zhang@unisoc.com>
Subject: Re: [PATCH V3 0/2] Add reattaching support and fix memory leak issue
Date: Mon, 27 Mar 2023 10:01:09 +0200	[thread overview]
Message-ID: <ZCFNRfpUHbaGBvJb@8bytes.org> (raw)
In-Reply-To: <CAAfSe-tg7JwakdCcoLn3Ws_164HcsT21pWHkjjw0Qqwy8PWkhQ@mail.gmail.com>


Hi Chunyan,

On Mon, Mar 27, 2023 at 10:47:18AM +0800, Chunyan Zhang wrote:
> Not sure if you received this patchset, since I received a rejection
> letter from mail.8bytes.org.
> 
> If you didn't receive it, I can resend it with another email address.
> 
> Otherwise, would you please pick up this series if there are no more comments.

I didn't receive it, can you please send me the error message you got
from my mail server?

Regards,

	Joerg

  reply	other threads:[~2023-03-27  8:01 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-13  7:50 [PATCH V3 0/2] Add reattaching support and fix memory leak issue Chunyan Zhang
2023-03-13  7:50 ` [PATCH V3 1/2] iommu: sprd: release dma buffer to avoid memory leak Chunyan Zhang
2023-03-13  7:50 ` [PATCH V3 2/2] iommu: sprd: Add support for reattaching an existing domain Chunyan Zhang
2023-03-27  2:47 ` [PATCH V3 0/2] Add reattaching support and fix memory leak issue Chunyan Zhang
2023-03-27  8:01   ` Joerg Roedel [this message]
2023-03-28  2:57     ` Chunyan Zhang
2023-03-28 13:13       ` Joerg Roedel

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=ZCFNRfpUHbaGBvJb@8bytes.org \
    --to=joro@8bytes.org \
    --cc=baolin.wang@linux.alibaba.com \
    --cc=baolu.lu@linux.intel.com \
    --cc=chunyan.zhang@unisoc.com \
    --cc=iommu@lists.linux.dev \
    --cc=linux-kernel@vger.kernel.org \
    --cc=orsonzhai@gmail.com \
    --cc=robin.murphy@arm.com \
    --cc=will@kernel.org \
    --cc=zhang.lyra@gmail.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