From: Tyrel Datwyler <tyreld@linux.ibm.com>
To: Michael Ellerman <mpe@ellerman.id.au>, tyreld@linux.vnet.ibm.com
Cc: brking@linux.vnet.ibm.com, james.bottomley@hansenpartnership.com,
linuxppc-dev@lists.ozlabs.org, martin.petersen@oracle.com,
linux-scsi@vger.kernel.org
Subject: Re: [PATCH] ibmvscsi: use GFP_KERNEL with dma_alloc_coherent in initialize_event_pool
Date: Fri, 15 Oct 2021 12:37:36 -0700 [thread overview]
Message-ID: <16d410ce-994e-0480-b764-27d0b21e51f3@linux.ibm.com> (raw)
In-Reply-To: <878ryuykd3.fsf@mpe.ellerman.id.au>
On 10/14/21 9:36 PM, Michael Ellerman wrote:
> Tyrel Datwyler <tyreld@linux.ibm.com> writes:
>> Just stumbled upon this trivial little patch that looks to have gotten lost in
>> the shuffle. Seems it even got a reviewed-by from Brian [1].
>>
>> So, uh I guess after almost 3 years...ping?
>
> It's marked "Changes Requested" here:
>
> https://patchwork.kernel.org/project/linux-scsi/patch/1547089149-20577-1-git-send-email-tyreld@linux.vnet.ibm.com/
Interesting
>
>
> If it isn't picked up in a few days you should probably do a resend so
> that it reappears in patchwork.
Fair enough
-Tyrel
>
> cheers
>
WARNING: multiple messages have this Message-ID (diff)
From: Tyrel Datwyler <tyreld@linux.ibm.com>
To: Michael Ellerman <mpe@ellerman.id.au>, tyreld@linux.vnet.ibm.com
Cc: brking@linux.vnet.ibm.com, james.bottomley@hansenpartnership.com,
linuxppc-dev@lists.ozlabs.org, linux-scsi@vger.kernel.org,
martin.petersen@oracle.com
Subject: Re: [PATCH] ibmvscsi: use GFP_KERNEL with dma_alloc_coherent in initialize_event_pool
Date: Fri, 15 Oct 2021 12:37:36 -0700 [thread overview]
Message-ID: <16d410ce-994e-0480-b764-27d0b21e51f3@linux.ibm.com> (raw)
In-Reply-To: <878ryuykd3.fsf@mpe.ellerman.id.au>
On 10/14/21 9:36 PM, Michael Ellerman wrote:
> Tyrel Datwyler <tyreld@linux.ibm.com> writes:
>> Just stumbled upon this trivial little patch that looks to have gotten lost in
>> the shuffle. Seems it even got a reviewed-by from Brian [1].
>>
>> So, uh I guess after almost 3 years...ping?
>
> It's marked "Changes Requested" here:
>
> https://patchwork.kernel.org/project/linux-scsi/patch/1547089149-20577-1-git-send-email-tyreld@linux.vnet.ibm.com/
Interesting
>
>
> If it isn't picked up in a few days you should probably do a resend so
> that it reappears in patchwork.
Fair enough
-Tyrel
>
> cheers
>
next prev parent reply other threads:[~2021-10-15 19:37 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-10 2:59 [PATCH] ibmvscsi: use GFP_KERNEL with dma_alloc_coherent in initialize_event_pool Tyrel Datwyler
2019-01-10 14:56 ` Brian King
2021-10-14 23:15 ` Tyrel Datwyler
2021-10-14 23:15 ` Tyrel Datwyler
2021-10-15 4:36 ` Michael Ellerman
2021-10-15 4:36 ` Michael Ellerman
2021-10-15 19:37 ` Tyrel Datwyler [this message]
2021-10-15 19:37 ` Tyrel Datwyler
2021-10-17 2:20 ` Martin K. Petersen
2021-10-17 2:20 ` Martin K. Petersen
2021-10-21 3:42 ` Martin K. Petersen
2021-10-21 3:42 ` Martin K. Petersen
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=16d410ce-994e-0480-b764-27d0b21e51f3@linux.ibm.com \
--to=tyreld@linux.ibm.com \
--cc=brking@linux.vnet.ibm.com \
--cc=james.bottomley@hansenpartnership.com \
--cc=linux-scsi@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=martin.petersen@oracle.com \
--cc=mpe@ellerman.id.au \
--cc=tyreld@linux.vnet.ibm.com \
/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.