From: Michael Ellerman <patch-notifications@ellerman.id.au>
To: Geoff Levand <geoff@infradead.org>,
Michael Ellerman <mpe@ellerman.id.au>
Cc: Jakub Kicinski <kuba@kernel.org>,
netdev@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
"David S. Miller" <davem@davemloft.net>
Subject: Re: [PATCH v2 0/3] DMA fixes for PS3 device drivers
Date: Fri, 18 Jun 2021 13:51:27 +1000 [thread overview]
Message-ID: <162398828712.1363949.1881698849429388448.b4-ty@ellerman.id.au> (raw)
In-Reply-To: <cover.1622746428.git.geoff@infradead.org>
On Thu, 03 Jun 2021 19:16:56 +0000, Geoff Levand wrote:
> This is a set of patches that fix various DMA related problems in the PS3
> device drivers, and add better error checking and improved message logging.
>
> Changes from V1:
> Split the V1 series into two, one series with powerpc changes, and one series
> with gelic network driver changes.
>
> [...]
Applied to powerpc/next.
[1/3] powerpc/ps3: Add CONFIG_PS3_VERBOSE_RESULT option
https://git.kernel.org/powerpc/c/6caebff168235b6102e5dc57cb95a2374301720a
[2/3] powerpc/ps3: Warn on PS3 device errors
https://git.kernel.org/powerpc/c/472b440fd26822c645befe459172dafdc2d225de
[3/3] powerpc/ps3: Add dma_mask to ps3_dma_region
https://git.kernel.org/powerpc/c/9733862e50fdba55e7f1554e4286fcc5302ff28e
cheers
WARNING: multiple messages have this Message-ID (diff)
From: Michael Ellerman <patch-notifications@ellerman.id.au>
To: Geoff Levand <geoff@infradead.org>,
Michael Ellerman <mpe@ellerman.id.au>
Cc: Jakub Kicinski <kuba@kernel.org>,
linuxppc-dev@lists.ozlabs.org,
"David S. Miller" <davem@davemloft.net>,
netdev@vger.kernel.org
Subject: Re: [PATCH v2 0/3] DMA fixes for PS3 device drivers
Date: Fri, 18 Jun 2021 13:51:27 +1000 [thread overview]
Message-ID: <162398828712.1363949.1881698849429388448.b4-ty@ellerman.id.au> (raw)
In-Reply-To: <cover.1622746428.git.geoff@infradead.org>
On Thu, 03 Jun 2021 19:16:56 +0000, Geoff Levand wrote:
> This is a set of patches that fix various DMA related problems in the PS3
> device drivers, and add better error checking and improved message logging.
>
> Changes from V1:
> Split the V1 series into two, one series with powerpc changes, and one series
> with gelic network driver changes.
>
> [...]
Applied to powerpc/next.
[1/3] powerpc/ps3: Add CONFIG_PS3_VERBOSE_RESULT option
https://git.kernel.org/powerpc/c/6caebff168235b6102e5dc57cb95a2374301720a
[2/3] powerpc/ps3: Warn on PS3 device errors
https://git.kernel.org/powerpc/c/472b440fd26822c645befe459172dafdc2d225de
[3/3] powerpc/ps3: Add dma_mask to ps3_dma_region
https://git.kernel.org/powerpc/c/9733862e50fdba55e7f1554e4286fcc5302ff28e
cheers
next prev parent reply other threads:[~2021-06-18 4:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-03 19:16 [PATCH v2 0/3] DMA fixes for PS3 device drivers Geoff Levand
2021-06-03 19:17 ` [PATCH v2 2/3] powerpc/ps3: Warn on PS3 device errors Geoff Levand
2021-06-03 19:17 ` [PATCH v2 1/3] powerpc/ps3: Add CONFIG_PS3_VERBOSE_RESULT option Geoff Levand
2021-06-03 19:17 ` [PATCH v2 3/3] powerpc/ps3: Add dma_mask to ps3_dma_region Geoff Levand
2021-06-18 3:51 ` Michael Ellerman [this message]
2021-06-18 3:51 ` [PATCH v2 0/3] DMA fixes for PS3 device drivers Michael Ellerman
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=162398828712.1363949.1881698849429388448.b4-ty@ellerman.id.au \
--to=patch-notifications@ellerman.id.au \
--cc=davem@davemloft.net \
--cc=geoff@infradead.org \
--cc=kuba@kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=netdev@vger.kernel.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.