From: Piotr Jaroszynski <pjaroszynski@nvidia.com>
To: Christoph Hellwig <hch@lst.de>
Cc: Dave Chinner <david@fromorbit.com>, linux-xfs@vger.kernel.org
Subject: Re: [PATCH] iomap: get/put the page in iomap_page_create/release()
Date: Sat, 19 Jan 2019 11:01:05 -0800 [thread overview]
Message-ID: <ef7e3ffd-2665-5924-79a8-18a31f02e264@nvidia.com> (raw)
In-Reply-To: <20190119094533.GA21729@lst.de>
On 1/19/19 1:45 AM, Christoph Hellwig wrote:
> On Thu, Jan 17, 2019 at 09:32:32AM -0800, Piotr Jaroszynski wrote:
>> On 1/16/19 11:51 PM, Christoph Hellwig wrote:
>>> On Wed, Jan 16, 2019 at 10:07:45AM +1100, Dave Chinner wrote:
>>>> Missing a SOB.
>>>>
>>>> But apart from that, I've been running an identical patch in my test
>>>> tree, so:
>>>
>>> Piotr: do you still want to claim authorship for this fixed up patch,
>>> in which case I'll need your sob. Otherwise I can submit it under my
>>> name.
>>
>> Sorry for the delay and thank you for handling the revert while I was
>> out on paternity leave. I'm fine with whatever is easiest for you,
>> and thanks for fixing up the patch!
>
> In that case I'll happily keep you as the author. Can you re-cofirm
> your signoff for this modified variant so we pick it up?
>
Sure:
Signed-off-by: Piotr Jaroszynski <pjaroszynski@nvidia.com>
Thanks,
Piotr
next prev parent reply other threads:[~2019-01-19 19:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-15 21:10 [PATCH] iomap: get/put the page in iomap_page_create/release() Christoph Hellwig
2019-01-15 23:07 ` Dave Chinner
2019-01-17 7:51 ` Christoph Hellwig
2019-01-17 17:32 ` Piotr Jaroszynski
2019-01-19 9:45 ` Christoph Hellwig
2019-01-19 19:01 ` Piotr Jaroszynski [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-01-21 15:17 Christoph Hellwig
2019-01-31 23:28 ` Darrick J. Wong
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=ef7e3ffd-2665-5924-79a8-18a31f02e264@nvidia.com \
--to=pjaroszynski@nvidia.com \
--cc=david@fromorbit.com \
--cc=hch@lst.de \
--cc=linux-xfs@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox