From: Marek Szyprowski <m.szyprowski@samsung•com>
To: 'Stephen Rothwell' <sfr@canb•auug.org.au>,
'Kyungmin Park' <kyungmin.park@samsung•com>
Cc: linux-next@vger•kernel.org, linux-kernel@vger•kernel.org
Subject: RE: linux-next: build failure after merge of the dma-mapping tree
Date: Mon, 13 Feb 2012 16:05:26 +0100 [thread overview]
Message-ID: <00dc01ccea60$ead06e30$c0714a90$%szyprowski@samsung.com> (raw)
In-Reply-To: <20120213164000.da84dfec7723af3a9eb3e13f@canb.auug.org.au>
Hi Stephen,
On Monday, February 13, 2012 6:40 AM Stephen Rothwell wrote:
> After merging the dma-mapping tree, today's linux-next build (powerpc
> ppc64_defconfig) failed like this:
(snipped)
I'm sorry for the problems. I've updated patches to fix these issues, as
well as similar problems with MIPS and Hexagon architecture.
Best regards
--
Marek Szyprowski
Samsung Poland R&D Center
next prev parent reply other threads:[~2012-02-13 15:05 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-13 5:40 linux-next: build failure after merge of the dma-mapping tree Stephen Rothwell
2012-02-13 7:31 ` Kyungmin Park
2012-02-13 15:05 ` Marek Szyprowski [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-11-27 6:58 Stephen Rothwell
2020-11-27 9:21 ` Christoph Hellwig
2020-11-27 9:59 ` Stephen Rothwell
2020-11-27 9:33 ` Christoph Hellwig
2024-05-07 23:16 Stephen Rothwell
2024-05-08 6:51 ` Christoph Hellwig
2024-05-08 8:51 ` Alexander Lobakin
2024-05-08 13:45 ` Christoph Hellwig
2024-07-10 1:05 Stephen Rothwell
2024-07-10 5:58 ` Christoph Hellwig
[not found] <CGME20260327200715eucas1p1953ce4c0b4d4e0cd95844f0acdb7ac3a@eucas1p1.samsung.com>
2026-03-27 20:07 ` Mark Brown
2026-03-30 7:56 ` Marek Szyprowski
2026-03-30 8:11 ` Maxime Ripard
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='00dc01ccea60$ead06e30$c0714a90$%szyprowski@samsung.com' \
--to=m.szyprowski@samsung$(echo .)com \
--cc=kyungmin.park@samsung$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=sfr@canb$(echo .)auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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