From: nick <xerofoify@gmail.com>
To: Rik van Riel <riel@redhat.com>,
Valdis.Kletnieks@vt.edu,
Catalin Marinas <catalin.marinas@arm.com>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mm:Avoid soft lockup due to possible attempt of double locking object's lock in __delete_object
Date: Tue, 6 Sep 2016 21:12:47 -0400 [thread overview]
Message-ID: <563d8230-4a58-cb5f-ef3e-b89745234252@gmail.com> (raw)
In-Reply-To: <1473209511.32433.179.camel@redhat.com>
On 2016-09-06 08:51 PM, Rik van Riel wrote:
> On Wed, 2016-08-31 at 17:28 -0400, nick wrote:
>>
>> Rather then argue since that will go nowhere. I am posing actual
>> patches that have been tested on
>> hardware.
>
> But not by you, apparently.
>
> The patch below was first posted by somebody else
> in 2013: https://lkml.org/lkml/2013/7/11/93
>
> When re-posting somebody else's patch, you need to
> preserve their From: and Signed-off-by: headers.
>
> See Documentation/SubmittingPatches for the details
> on that.
>
> Pretending that other people's code is your own
> is not only very impolite, it also means that
> the origin of the code, and permission to distribute
> it under the GPL, are in question.
>
> Will you promise to not claim other people's code as
> your own?
>
I wasn't aware of that. Seems it was fixed before I got to
it but was never merged. Next time I will double check if the
patch work is already out there. Also have this patch but the
commit message needs to be reworked:
next prev parent reply other threads:[~2016-09-07 1:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-30 18:35 Nicholas Krause
2016-08-31 7:54 ` Catalin Marinas
2016-08-31 13:24 ` nick
2016-09-07 0:45 ` Rik van Riel
2016-08-31 13:41 ` nick
2016-08-31 14:35 ` Catalin Marinas
2016-08-31 21:08 ` Valdis.Kletnieks
2016-08-31 21:28 ` nick
2016-09-07 0:51 ` Rik van Riel
2016-09-07 1:12 ` nick [this message]
2016-09-07 1:22 ` Rik van Riel
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=563d8230-4a58-cb5f-ef3e-b89745234252@gmail.com \
--to=xerofoify@gmail.com \
--cc=Valdis.Kletnieks@vt.edu \
--cc=catalin.marinas@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=riel@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox