From: Greg KH <gregkh@linuxfoundation.org>
To: obayashi.yoshimasa@socionext.com
Cc: sumit.garg@linaro.org, hch@lst.de, m.szyprowski@samsung.com,
robin.murphy@arm.com, iommu@lists.linux-foundation.org,
linux-kernel@vger.kernel.org, stable@vger.kernel.org,
daniel.thompson@linaro.org
Subject: Re: DMA direct mapping fix for 5.4 and earlier stable branches
Date: Tue, 9 Feb 2021 10:23:12 +0100 [thread overview]
Message-ID: <YCJUgKDNVjJ4dUqM@kroah.com> (raw)
In-Reply-To: <27bbe35deacb4ca49f31307f4ed551b5@SOC-EX02V.e01.socionext.com>
On Tue, Feb 09, 2021 at 09:05:40AM +0000, obayashi.yoshimasa@socionext.com wrote:
> > > As the drivers are currently under development and Socionext has
> > > chosen 5.4 stable kernel for their development. So I will let
> > > Obayashi-san answer this if it's possible for them to migrate to 5.10
> > > instead?
>
> We have started this development project from last August,
> so we have selected 5.4 as most recent and longest lifetime LTS
> version at that time.
>
> And we have already finished to develop other device drivers,
> and Video converter and CODEC drivers are now in development.
>
> > Why pick a kernel that doesn not support the features they require?
> > That seems very odd and unwise.
>
> From the view point of ZeroCopy using DMABUF, is 5.4 not
> mature enough, and is 5.10 enough mature ?
> This is the most important point for judging migration.
How do you judge "mature"?
And again, if a feature isn't present in a specific kernel version, why
would you think that it would be a viable solution for you to use?
good luck!
greg k-h
next prev parent reply other threads:[~2021-02-09 9:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-09 6:09 DMA direct mapping fix for 5.4 and earlier stable branches Sumit Garg
2021-02-09 6:58 ` Greg Kroah-Hartman
2021-02-09 7:58 ` Sumit Garg
2021-02-09 8:04 ` Greg Kroah-Hartman
2021-02-09 9:05 ` obayashi.yoshimasa
2021-02-09 9:23 ` Greg KH [this message]
2021-02-09 9:36 ` Christoph Hellwig
2021-02-09 12:36 ` Sumit Garg
2021-02-09 12:45 ` Robin Murphy
2021-02-09 15:50 ` Christoph Hellwig
2021-02-09 10:19 ` obayashi.yoshimasa
2021-02-09 10:39 ` Greg KH
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=YCJUgKDNVjJ4dUqM@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=daniel.thompson@linaro.org \
--cc=hch@lst.de \
--cc=iommu@lists.linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=obayashi.yoshimasa@socionext.com \
--cc=robin.murphy@arm.com \
--cc=stable@vger.kernel.org \
--cc=sumit.garg@linaro.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