From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751407AbdJENtG (ORCPT ); Thu, 5 Oct 2017 09:49:06 -0400 Received: from Galois.linutronix.de ([146.0.238.70]:34118 "EHLO Galois.linutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751280AbdJENtF (ORCPT ); Thu, 5 Oct 2017 09:49:05 -0400 Date: Thu, 5 Oct 2017 15:48:59 +0200 (CEST) From: Thomas Gleixner To: Doug Ledford cc: Kees Cook , linux-kernel@vger.kernel.org, Faisal Latif , Sean Hefty , Hal Rosenstock , linux-rdma@vger.kernel.org Subject: Re: [PATCH] RDMA/nes: Convert timers to use timer_setup() In-Reply-To: <622bfd9d-69df-9d78-d72b-5bd49d979afa@redhat.com> Message-ID: References: <20171005004527.GA22607@beast> <622bfd9d-69df-9d78-d72b-5bd49d979afa@redhat.com> User-Agent: Alpine 2.20 (DEB 67 2015-01-07) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, 5 Oct 2017, Doug Ledford wrote: > On 10/4/2017 8:45 PM, Kees Cook wrote: > > In preparation for unconditionally passing the struct timer_list pointer to > > all timer callbacks, switch to using the new timer_setup() and from_timer() > > to pass the timer pointer explicitly. A pointer from nesadapter back to > > nesdev was added. > > > > Cc: Faisal Latif > > Cc: Doug Ledford > > Cc: Sean Hefty > > Cc: Hal Rosenstock > > Cc: linux-rdma@vger.kernel.org > > Cc: Thomas Gleixner > > Signed-off-by: Kees Cook > > --- > > This requires commit 686fef928bba ("timer: Prepare to change timer > > callback argument type") in v4.14-rc3, but should be otherwise > > stand-alone. > > What is your intention with this, and the other RDMA related, patches? > Is it your intention that I should pick these up or is someone else > supposed to (you sent it to linux-kernel and only Cc:ed linux-rdma)? > Also, are you intending this to go into -rc? If so, why is it dependent > on a patch that didn't land until -rc3? That's 4.15 material and should preferrably be picked up by the relevant maintainers. The 4.14-rc3 reference is there just in case a maintainer tree is based on pre 4.14-rc3, so applying the patch would break the build. Thanks, tglx