Received: by 2002:ac0:a5a7:0:0:0:0:0 with SMTP id m36-v6csp303708imm; Sat, 14 Jul 2018 00:46:19 -0700 (PDT) X-Google-Smtp-Source: AAOMgpfL43TaLrLCTtUwKjJBSQKLYtbmDsWBLuKOEZL1Vuh+PCSYkWGyDCzas63xPr63mXcSBofo X-Received: by 2002:a17:902:7202:: with SMTP id ba2-v6mr7359805plb.179.1531554379221; Sat, 14 Jul 2018 00:46:19 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1531554379; cv=none; d=google.com; s=arc-20160816; b=enNuilV5b1MxtO+v/vT7j0Wc6y8ePlJgCm0DVEDfjntCVlYTb0+NoHA652qssr5E4v DE3DmED/X7dwQcCYyvcBzYQ3ZbMG/Qx46JOr88dBK1ITrxvoE2N3dOrmtf/upLdecyu1 gjtOsLN9ngwk1YQZcuptRxe7VCQxh3mK1VHuwP2r3YCx32W+5FLeUXktPXwPAq3F9dEz 1q1TJNHU5h/908XouGgUkDLAgGpKj64LiShumCMrrP8JFEAI+owoI7YjrkGSdMjJ7pR5 S+tNLef4don0EG83bsYS7xiEzfd832jCDR5Q8C+CCPQO/1McnM/k54aNkOAT3WASunkH JIBA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-transfer-encoding:content-disposition:mime-version :references:message-id:subject:cc:to:from:date :arc-authentication-results; bh=TCI7SgtNDPoa2+si5Tm93QDMv55GqsxKYASdRoEXufM=; b=fpJKL6EP0KTU9PZC4O8w6PTvZxFTyLdCRAnSFzRZPVu0y3vX1J28ev/4sCa/gAX/2+ 7oIKfZ7uGhhZDS1wUNoAUYiTG8wtG2rldY/GLReXaWv48Y1juFXCmdDIxeQYnLn9ekV2 NNUp1eSFdhVnE7cxvKb/Eo0VZKUDagXZSuX1NuHp9uRuQvmx5jus+vjWIypy6TDVLxJV vA088nPUdhD43+JsEWO/bFP3VvjtHoiYJ/5EkxLm0/HiBPDVU9p4KNULBuAEJ7JMmB9B M8Q1Z8H2jErJTI+LFhwXdPLcAbznAm1JwpbfKVE66cpRoH+Rxgt5c3l8YG9uUMNGzxfW Zu3g== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id 2-v6si24882807pgq.479.2018.07.14.00.45.50; Sat, 14 Jul 2018 00:46:19 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726149AbeGNIDB (ORCPT + 99 others); Sat, 14 Jul 2018 04:03:01 -0400 Received: from mail.linuxfoundation.org ([140.211.169.12]:56766 "EHLO mail.linuxfoundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725913AbeGNIDB (ORCPT ); Sat, 14 Jul 2018 04:03:01 -0400 Received: from localhost (LFbn-1-12247-202.w90-92.abo.wanadoo.fr [90.92.61.202]) by mail.linuxfoundation.org (Postfix) with ESMTPSA id DC3F28A5; Sat, 14 Jul 2018 07:44:52 +0000 (UTC) Date: Sat, 14 Jul 2018 09:44:50 +0200 From: Greg Kroah-Hartman To: Todd Poynor Cc: Rob Springer , John Joseph , Ben Chan , devel@driverdev.osuosl.org, Zhongze Hu , linux-kernel@vger.kernel.org, Simon Que , Guenter Roeck , Todd Poynor , Dmitry Torokhov Subject: Re: [PATCH 12/18] staging: gasket: annotate ioctl arg with __user Message-ID: <20180714074450.GA22469@kroah.com> References: <20180714055816.223754-1-toddpoynor@gmail.com> <20180714055816.223754-13-toddpoynor@gmail.com> <20180714063502.GF20451@kroah.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: Mutt/1.10.0 (2018-05-17) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sat, Jul 14, 2018 at 12:12:38AM -0700, Todd Poynor wrote: HTML email gets rejected by the mailing lists :( Please fix your email client to not do that. > On Fri, Jul 13, 2018 at 11:35 PM, Greg Kroah-Hartman < > gregkh@linuxfoundation.org> wrote: > > On Fri, Jul 13, 2018 at 10:58:10PM -0700, Todd Poynor wrote: > > From: Todd Poynor > > > > For sparse checking. > > > > Reported-by: Dmitry Torokhov > > Signed-off-by: Zhongze Hu > > Signed-off-by: Todd Poynor > > --- > > Are you sure this patch even applies?? What tree did you make it > against? > > > I'm working in linux-next at tag next-20180713, which is also tagged master at > this writing.? > > I think I'm following http://www.kroah.com/log/linux/linux-staging-update.html, > but if I'm off in the weeds do clue me in, thanks.? That's something I wrote 9 years ago :) Anyway, yes, linux-next is usually the right place to work off of, but it lags my staging.git tree usually by at least a day, maybe two, depending on when I push and when -next picks my tree up. Also there is the lag of the weekend when -next is not being generated. Normally that is fine, except for when working on code that is "fast moving". This driver has had lots of submissions against it lately as there are loads of "low hanging fruit" that people easily see to fix up. Look at the mailing list archives for this week alone for all of those patches. When working on something that lots of other people are working on, pay attention to the patches on the mailing list and work off of my staging.git tree, usually the staging-next branch, but sometimes staging-testing is needed if lots of patches are being sent rapidly. > I ask because this fragment: > > > @@ -12,6 +12,7 @@ > >? ?* GNU General Public License for more details. > >? ?*/ > > is no longer in the tree. > > > Sorry, which tree?? I've made sure my linux-next is up-to-date and I still see > this code. Look at my staging-next branch in staging.git. It's long-gone :) thanks, greg k-h