From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-2.3 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,FREEMAIL_FORGED_FROMDOMAIN,FREEMAIL_FROM, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS, USER_AGENT_SANE_1 autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 81A0AC10DCE for ; Thu, 12 Mar 2020 14:39:25 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 55CC9206B1 for ; Thu, 12 Mar 2020 14:39:25 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=gmail.com header.i=@gmail.com header.b="LIvMy9yG" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727467AbgCLOjZ (ORCPT ); Thu, 12 Mar 2020 10:39:25 -0400 Received: from mail-wr1-f68.google.com ([209.85.221.68]:35614 "EHLO mail-wr1-f68.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727514AbgCLOjY (ORCPT ); Thu, 12 Mar 2020 10:39:24 -0400 Received: by mail-wr1-f68.google.com with SMTP id d5so7453266wrc.2; Thu, 12 Mar 2020 07:39:23 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding:content-language; bh=Gh68Trk0v1VLiAj6jDTGi0HWdz0Xo0dSTWDaOMm1MTw=; b=LIvMy9yGVZS4Ff7qe030zT5MGioQil0x/ntqKRVbs/0DuarcdPb8iUCe6m36CDbCVG gfyMwbvb7pzqHndVHhVrvtV5VSxyBdspyYsnDUTpPprK23HjP9UDezOu08708IXtadRS jBiTuILhvPxhxdchFvTBDPkGF6Fj9aL6qP349QFgOLaNo1W/EIr5y7TQzu837KdbAbCC JqIDUA5NPHwqxC5Q3EYLcoJNig194jeNcZZqX7NIYr7rFes8fCjMyC8IfQRnVa9WEFDl kkL6Nhdvb6HdKbnMt0vgMEkw9k+s4d+7Y3kX50ef2g87/Dpum6/OkTqvmUnBp7O2ETwT dmdQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding :content-language; bh=Gh68Trk0v1VLiAj6jDTGi0HWdz0Xo0dSTWDaOMm1MTw=; b=PNzZOu88/mKkVcki50ZNFv+870h5gdpGq6akQP1hj9B6gHUTuOz6vFACi2KQ3ftH4B A2zRxoZFKwVdyNj7QOcEaBSV8CBsJtAWPxQxF/RZlB68hRXQX2KFbKWmXQquVHV9Wz5Z SsCn9y0/J4K9bXkppstPKCxlIN4bDMYEvLONRAc9iCx4ZWZtDCl9orDV6AKp7jRkPEfS cyADSPYyECM+p4QZ9GXvrV/PsBNX0lcAxuOR27QjUiUFU+/fDAXaccAFM9FoOAsDbemd 3fypbNckvBSzHt8tFfY+41x7Sahr2VQD+pdJw9FTyTx9v5yn6uDZhH7m9eemzwNmfIF2 Qdcw== X-Gm-Message-State: ANhLgQ2v4RZ7OXkpjzXgBptDvM2UgA21IwBvIcQaVjDLCvgjWQuzJ1MR rEnYIgVEHl2lxhUjxvlh8MEDTfh7+i4cvw== X-Google-Smtp-Source: ADFU+vtd6pFHy8us6TRQj7Sj0ZChzcReBnODNWMt6SuYH+Snk6tVg1B51+V/2fjT4roFTLE5Xa2e0Q== X-Received: by 2002:a5d:6a0e:: with SMTP id m14mr11537032wru.202.1584023962390; Thu, 12 Mar 2020 07:39:22 -0700 (PDT) Received: from [10.7.1.8] ([37.58.58.229]) by smtp.gmail.com with ESMTPSA id c8sm66848031wru.7.2020.03.12.07.39.21 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 12 Mar 2020 07:39:21 -0700 (PDT) Subject: Re: [PATCH] gpio-hammer: Avoid potential overflow in main To: Bartosz Golaszewski Cc: Linus Walleij , linux-gpio , LKML References: <20200312094008.1833929-1-gabravier@gmail.com> <38cbabe3-151b-1fd6-9d36-f27e9c9aa414@gmail.com> <55db9307-9a20-239e-127c-ea043600248d@gmail.com> From: Gabriel Ravier Message-ID: Date: Thu, 12 Mar 2020 15:39:20 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.5.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US Sender: linux-gpio-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-gpio@vger.kernel.org On 3/12/20 3:36 PM, Bartosz Golaszewski wrote: > czw., 12 mar 2020 o 15:33 Gabriel Ravier napisał(a): >> Ah, seems like I didn't read the guide to getting code into the kernel >> thoroughly enough. Should I send the patch yet again just with a v2 in >> the subject header or is there no need to bother with that ? >> > Please do so that patchwork picks it up. Also: please don't top-post > on LKML ie. respond below others' text. > > Bart Ok, will send it with s/PATCH/PATCH v2 ASAP. Btw, is the "top-posting" the reason why lkml.org doesn't seem to be able to find my replies to your posts ?