From: mingo@kernel.org (Ingo Molnar)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4 0/7] enable support for AMBA drivers under x86
Date: Mon, 6 May 2013 11:41:54 +0200 [thread overview]
Message-ID: <20130506094154.GA9464@gmail.com> (raw)
In-Reply-To: <20130505203932.GA12742@pd.tnic>
* Borislav Petkov <bp@alien8.de> wrote:
> On Sun, May 05, 2013 at 10:24:22PM +0200, Alessandro Rubini wrote:
> > > Did this got fixed in some tree in the meantime? Because I still see it on
> > > current Linus + tip/master:
> > >
> > > arch/x86/pci/sta2x11-fixup.c:186:2: warning: initialization from incompatible pointer type [enabled by default]
> > > arch/x86/pci/sta2x11-fixup.c:186:2: warning: (near initialization for ??????sta2x11_dma_ops.free??????) [enabled by default]
> >
> > Last time I sent the patch was on Feb 22nd:
> >
> > The .free field of struct dma_map_ops features a prototype that is
> > different from what lib/swiotlb.c offers. The new "attrs" argument in
> > dma_ops.free is missing from the generic implementation.
> >
> > This removes the build warning by providing a function that just calls
> > swiotlb_free_coherent() without passing "attrs", like others do.
> >
> > I got no reply.
>
> It probably fell through the cracks...
>
> > This is the link:
> >
> > http://lkml.org/lkml/2013/2/22/111
> >
> > It is in patchwork here:
> >
> > https://patchwork.kernel.org/patch/2175551/
>
> Ingo, hpa, can you guys pick it up?
A lot happened meanwhile - patches got acked, applied - so I expected a
resend of the patches that are still pending, with all acks in place in
the patches (not in the cover letter), and against Linus's latest tree.
Thanks,
Ingo
next prev parent reply other threads:[~2013-05-06 9:41 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-10 13:42 [PATCH v4 0/7] enable support for AMBA drivers under x86 Davide Ciminaghi
2012-12-10 13:42 ` [PATCH v4 1/7] DMA: PL330: use prefix in reg names to build " Davide Ciminaghi
2012-12-11 4:25 ` Jassi Brar
2012-12-10 13:42 ` [PATCH v4 2/7] pl080.h: moved from arm/include/asm/hardware to include/linux/amba/ Davide Ciminaghi
2012-12-10 21:44 ` Linus Walleij
2012-12-10 22:25 ` Davide Ciminaghi
2013-01-13 13:25 ` Vinod Koul
2012-12-10 13:42 ` [PATCH v4 3/7] watchdog: sp805_wdt depends on ARM Davide Ciminaghi
[not found] ` <20121212212124.GB31853@spo001.leaseweb.com>
2012-12-12 22:20 ` Grant Likely
2012-12-10 13:42 ` [PATCH v4 4/7] mmci: replace readsl/writesl with ioread32_rep/iowrite32_rep Davide Ciminaghi
2012-12-10 13:42 ` [PATCH v4 5/7] mmc: use the new <linux/sizes.h> Davide Ciminaghi
2012-12-10 13:42 ` [PATCH v4 6/7] drivers/amba: add support for a PCI bridge Davide Ciminaghi
2012-12-10 13:42 ` [PATCH v4 7/7] x86: add CONFIG_ARM_AMBA, selected by STA2X11 Davide Ciminaghi
2012-12-13 0:48 ` H. Peter Anvin
2012-12-10 22:15 ` [PATCH v4 0/7] enable support for AMBA drivers under x86 David Brown
2012-12-13 0:37 ` H. Peter Anvin
2012-12-13 1:10 ` Grant Likely
2012-12-13 1:16 ` H. Peter Anvin
2012-12-13 2:02 ` H. Peter Anvin
2012-12-13 2:16 ` H. Peter Anvin
2012-12-13 18:14 ` Alessandro Rubini
2013-05-05 12:36 ` Borislav Petkov
2013-05-05 20:24 ` Alessandro Rubini
2013-05-05 20:39 ` Borislav Petkov
2013-05-06 9:41 ` Ingo Molnar [this message]
2013-05-06 10:11 ` Borislav Petkov
2013-05-06 9:54 ` Alessandro Rubini
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=20130506094154.GA9464@gmail.com \
--to=mingo@kernel.org \
--cc=linux-arm-kernel@lists.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 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).