From: Marek Szyprowski <m.szyprowski@samsung.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL] DMA-mapping updates for v3.11
Date: Wed, 03 Jul 2013 09:58:37 +0200 [thread overview]
Message-ID: <51D3D9AD.9070800@samsung.com> (raw)
In-Reply-To: <20130703100903.81ab08c6db864c20498b558d@canb.auug.org.au>
Hi Stephen,
On 7/3/2013 2:09 AM, Stephen Rothwell wrote:
> Hi Marek,
>
> On Tue, 02 Jul 2013 10:35:08 +0200 Marek Szyprowski <m.szyprowski@samsung.com> wrote:
> >
> > I would like to ask You for pulling some fixes for ARM dma-mapping subsystem
> > for v3.11.
> >
> >
> > The following changes since commit 8bb495e3f02401ee6f76d1b1d77f3ac9f079e376:
> >
> > Linux 3.10 (2013-06-30 15:13:29 -0700)
> >
> > are available in the git repository at:
> >
> > git://git.linaro.org/people/mszyprowski/linux-dma-mapping.git for-v3.11
> >
> > for you to fetch changes up to 1e3d09b223f349a5f6cc14d62b4df66c0798d762:
> >
> > ARM: dma: Drop __GFP_COMP for iommu dma memory allocations (2013-07-02 10:30:59 +0200)
>
> This was rebased yesterday onto v3.10 for some reason (one commit was
> dropped in the rebase).
Right, I dropped one commit, which I found in other 'for_next' kernel
tree (the
one from Russell King) before sending the pull request. What's wrong
with this
approach?
Best regards
--
Marek Szyprowski
Samsung R&D Institute Poland
next prev parent reply other threads:[~2013-07-03 7:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-02 8:35 [GIT PULL] DMA-mapping updates for v3.11 Marek Szyprowski
2013-07-03 0:09 ` Stephen Rothwell
2013-07-03 7:58 ` Marek Szyprowski [this message]
2013-07-03 21:02 ` Linus Torvalds
2013-07-04 6:09 ` Marek Szyprowski
-- strict thread matches above, loose matches on Subject: below --
2013-07-05 15:31 Marek Szyprowski
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=51D3D9AD.9070800@samsung.com \
--to=m.szyprowski@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=torvalds@linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.