Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Subject: Re: [PATCH] tipc: use consistent GFP flags
From:   patchwork-bot+netdevbpf@kernel.org
Message-Id: <163698120846.10163.14371622974741533436.git-patchwork-notify@kernel.org>
Date:   Mon, 15 Nov 2021 13:00:08 +0000
References: <20211111205916.37899-2-tadeusz.struk@linaro.org>
In-Reply-To: <20211111205916.37899-2-tadeusz.struk@linaro.org>
To:     Tadeusz Struk <tadeusz.struk@linaro.org>
Cc:     jmaloy@redhat.com, ying.xue@windriver.com, davem@davemloft.net,
        kuba@kernel.org, netdev@vger.kernel.org,
        tipc-discussion@lists.sourceforge.net, linux-kernel@vger.kernel.org
Precedence: bulk

Hello:

This patch was applied to netdev/net.git (master)
by David S. Miller <davem@davemloft.net>:

On Thu, 11 Nov 2021 12:59:16 -0800 you wrote:
> Some functions, like tipc_crypto_start use inconsisten GFP flags
> when allocating memory. The mentioned function use GFP_ATOMIC to
> to alloc a crypto instance, and then calls alloc_ordered_workqueue()
> which allocates memory with GFP_KERNEL. tipc_aead_init() function
> even uses GFP_KERNEL and GFP_ATOMIC interchangeably.
> No doc comment specifies what context a function is designed to
> work in, but the flags should at least be consistent within a function.
> 
> [...]

Here is the summary with links:
  - tipc: use consistent GFP flags
    https://git.kernel.org/netdev/net/c/86c3a3e964d9

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html