From: Takashi Iwai <tiwai@suse.de>
To: Christoph Hellwig <hch@lst.de>
Cc: Takashi Iwai <tiwai@suse.de>,
Stephen Rothwell <sfr@canb.auug.org.au>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: build failure after merge of the sound tree
Date: Fri, 17 Jul 2020 08:54:12 +0200 [thread overview]
Message-ID: <s5h4kq6ljhn.wl-tiwai@suse.de> (raw)
In-Reply-To: <20200717065030.GA10829@lst.de>
On Fri, 17 Jul 2020 08:50:30 +0200,
Christoph Hellwig wrote:
>
> On Fri, Jul 17, 2020 at 08:34:47AM +0200, Takashi Iwai wrote:
> > On Fri, 17 Jul 2020 07:33:24 +0200,
> > Christoph Hellwig wrote:
> > >
> > > On Fri, Jul 17, 2020 at 01:01:12PM +1000, Stephen Rothwell wrote:
> > > > Hi all,
> > > >
> > > > After merging the sound tree, today's linux-next build (x86_64
> > > > allmodconfig) failed like this:
> > >
> > > No, the sound commit needs to be reverted. Drivers has absolutely not
> > > business poking into DMA layer internals.
> >
> > OK, I'll drop that stuff again. It was the thing posted in the thread
> > of DMA regression with AMD SEV on 5.8-rc1. Meanwhile it was fixed in
> > the proper Kconfig dependency.
>
> We have other x86 changes that will not support just remapping stuff
> ignoring the API in the pipe, so this will need to get sorted out. And
> with that I mean sorted out properly instead of poking into undocumented
> DMA API internals and coming to the wrong conclusions again..
OK, when a proper API (or some kconfig) is ready for referring from
the driver side, let me know. I'd love to keep the SG-buffer support
as much as possible, since HD-audio stuff has been used for a very old
machine with a small RAM.
thanks,
Takashi
next prev parent reply other threads:[~2020-07-17 6:54 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-17 3:01 linux-next: build failure after merge of the sound tree Stephen Rothwell
2020-07-17 5:33 ` Christoph Hellwig
2020-07-17 6:34 ` Takashi Iwai
2020-07-17 6:50 ` Christoph Hellwig
2020-07-17 6:54 ` Takashi Iwai [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-08-18 3:12 Stephen Rothwell
2023-08-18 11:47 ` Takashi Iwai
2023-05-24 3:54 Stephen Rothwell
2023-05-24 7:14 ` Takashi Iwai
2022-07-15 12:44 Stephen Rothwell
2022-07-15 14:41 ` Takashi Iwai
2022-07-15 19:09 ` Andy Shevchenko
2021-10-18 0:38 Stephen Rothwell
2021-10-18 6:35 ` Takashi Iwai
2019-08-09 2:54 Stephen Rothwell
2019-08-09 5:55 ` Takashi Iwai
2017-05-17 1:29 Stephen Rothwell
2017-05-17 5:30 ` Takashi Iwai
2011-09-23 2:49 Stephen Rothwell
2011-09-23 5:21 ` Takashi Iwai
2011-05-19 1:15 Stephen Rothwell
2010-09-23 2:44 Stephen Rothwell
2010-09-23 6:04 ` Takashi Iwai
2010-09-23 8:39 ` Mark Brown
2010-06-24 3:03 Stephen Rothwell
2010-06-24 6:11 ` Takashi Iwai
2010-06-28 16:33 ` Daniel Mack
2010-06-01 2:30 Stephen Rothwell
2010-06-01 5:47 ` Takashi Iwai
2010-04-07 3:39 Stephen Rothwell
2010-04-07 6:06 ` Takashi Iwai
2010-04-07 7:16 ` Stephen Rothwell
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=s5h4kq6ljhn.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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).