From: Greg KH <gregkh@linuxfoundation.org>
To: Chanho Park <chanho61.park@samsung.com>
Cc: "Bumyong Lee" <bumyong.lee@samsung.com>,
"Christoph Hellwig" <hch@lst.de>,
"Dominique MARTINET" <dominique.martinet@atmark-techno.com>,
"Horia Geantă" <horia.geanta@nxp.com>,
stable@vger.kernel.org,
"Konrad Rzeszutek Wilk" <konrad.wilk@oracle.com>
Subject: Re: [PATCH] swiotlb: manipulate orig_addr when tlb_addr has offset
Date: Mon, 28 Jun 2021 11:05:57 +0200 [thread overview]
Message-ID: <YNmQ9ZmZS658Rxfi@kroah.com> (raw)
In-Reply-To: <513700442.21624870682149.JavaMail.epsvc@epcpadp4>
On Mon, Jun 28, 2021 at 03:59:16PM +0900, Chanho Park wrote:
> From: Bumyong Lee <bumyong.lee@samsung.com>
>
> commit 5f89468e2f060031cd89fd4287298e0eaf246bf6 upstream.
> (Backported as different form due to absence of below patch series
> https://lore.kernel.org/linux-iommu/20210301074436.919889-1-hch@lst.de/)
What stable kernel(s) is this for?
And did you send the same patch twice?
thanks,
greg k-h
next prev parent reply other threads:[~2021-06-28 9:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-25 9:26 FAILED: patch "[PATCH] swiotlb: manipulate orig_addr when tlb_addr has offset" failed to apply to 5.12-stable tree gregkh
[not found] ` <CGME20210628065823epcas2p19305f8b888a7fc0e883ec51db61e3bae@epcas2p1.samsung.com>
2021-06-28 6:59 ` [PATCH] swiotlb: manipulate orig_addr when tlb_addr has offset Chanho Park
2021-06-28 9:05 ` Greg KH [this message]
2021-06-28 9:25 ` Chanho Park
2021-06-28 9:36 ` 'Greg KH'
2021-06-28 10:05 ` Chanho Park
2021-06-28 12:20 ` 'Greg KH'
-- strict thread matches above, loose matches on Subject: below --
2021-06-25 9:26 FAILED: patch "[PATCH] swiotlb: manipulate orig_addr when tlb_addr has offset" failed to apply to 5.10-stable tree gregkh
[not found] ` <CGME20210628065652epcas2p28f39187d9c1519cea42bd99a7e9dd75d@epcas2p2.samsung.com>
2021-06-28 6:57 ` [PATCH] swiotlb: manipulate orig_addr when tlb_addr has offset Chanho Park
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=YNmQ9ZmZS658Rxfi@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=bumyong.lee@samsung.com \
--cc=chanho61.park@samsung.com \
--cc=dominique.martinet@atmark-techno.com \
--cc=hch@lst.de \
--cc=horia.geanta@nxp.com \
--cc=konrad.wilk@oracle.com \
--cc=stable@vger.kernel.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 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).