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=-0.9 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE, SPF_PASS 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 C8C42C2BA12 for ; Fri, 3 Apr 2020 21:18:40 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 9A37120719 for ; Fri, 3 Apr 2020 21:18:40 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=linaro.org header.i=@linaro.org header.b="dQEiMd49" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727977AbgDCVSj (ORCPT ); Fri, 3 Apr 2020 17:18:39 -0400 Received: from mail-pg1-f195.google.com ([209.85.215.195]:39535 "EHLO mail-pg1-f195.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727842AbgDCVSj (ORCPT ); Fri, 3 Apr 2020 17:18:39 -0400 Received: by mail-pg1-f195.google.com with SMTP id g32so4160482pgb.6 for ; Fri, 03 Apr 2020 14:18:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to; bh=wh5T6yPyoIGG+Zj0KpPrWCt6Ri24iIgqMcr/FSjIJjo=; b=dQEiMd49xF9NMr54YPZPEh4RazLTQFxG6S/9P9F88Xuirh9ym2aWmtBdghXexh1frW z/rgzY+sOVKm3vlHmNr71rvnMGgJRvyjZQYdHQmMI+CtLIVqT+r4WtrEpKhgXGQXZwnA AOyQ+znPhKYs1ui2r43DlnnZ7xfyeaDB4uXqdvuTQG+aTdxydM1S1InyhLvsRaVLxMkT vwjfTQB3iDUix3tGh22PHsg3qYgYNHJ4ePCmqZug/IzvED7jgumdbep2Cvgil7y0lxC1 6vQrzBFEzlPxDtZpLVT70OjLcwAxbRdmnuHcF6towIOeUCmYRxnFMG6kmapOOYAyskBM NkYw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to; bh=wh5T6yPyoIGG+Zj0KpPrWCt6Ri24iIgqMcr/FSjIJjo=; b=cwMYCS2Vcbn09a6Ohrrqi5oFwDSKFLPc9o9JNkpxB2Tu1VDsGHei8fDJm5GfvN1YK5 C+SFG7Fwzwq1mM5cnMfZtvdJvlgRq44JAeuwUNj1HEQ/lU2DBwIDSmaezxxYR7vNsClF cT65dFCaWauG1O07VIEd5gHSertMY3QsVOgHT82tgjH5v9TMefYZBc6YnJU03N23ePmC hBT83G1oFxHovI8k8xx2OpJL+zxwFW9SVfB0RStv/YI4YQWOQdiJC5/xvDtcgWIntEs2 QmfPv5K9Rraa0YHgrm5vVIfRYWREXhY/NFyl/zVR+BZ6dbxZR+shQeRsAN6RosfQ4E+3 tP8Q== X-Gm-Message-State: AGi0PuahpWgjmVmwYnCz9Y6lRrVlWr+k3yOCe8EF0ZHYLOzAfcVnFbMY otsf2t4UT/gfKqrcZwSpq8rIFib3YqU= X-Google-Smtp-Source: APiQypJXDWUKp+Nep+BHCEq3Oh0B9wkDEQHXI5BOrNimox2vgXjNvj7+clayV+Yw4Dt6ILYEscXZRA== X-Received: by 2002:a63:a052:: with SMTP id u18mr10351993pgn.210.1585948717780; Fri, 03 Apr 2020 14:18:37 -0700 (PDT) Received: from builder.lan (104-188-17-28.lightspeed.sndgca.sbcglobal.net. [104.188.17.28]) by smtp.gmail.com with ESMTPSA id y15sm6406323pfc.206.2020.04.03.14.18.36 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 03 Apr 2020 14:18:37 -0700 (PDT) Date: Fri, 3 Apr 2020 14:18:37 -0700 From: Bjorn Andersson To: Linus Torvalds Cc: Nathan Chancellor , Ohad Ben-Cohen , linux-remoteproc@vger.kernel.org, Linux Kernel Mailing List Subject: Re: [PATCH] remoteproc/omap: Fix set_load call in omap_rproc_request_timer Message-ID: <20200403211837.GC20625@builder.lan> References: <20200402010812.GA751391@yoga> <20200403013134.11407-1-natechancellor@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri 03 Apr 10:48 PDT 2020, Linus Torvalds wrote: > On Thu, Apr 2, 2020 at 6:32 PM Nathan Chancellor > wrote: > > > > This is due to commit 02e6d546e3bd ("clocksource/drivers/timer-ti-dm: > > Enable autoreload in set_pwm") in the clockevents tree interacting with > > commit e28edc571925 ("remoteproc/omap: Request a timer(s) for remoteproc > > usage") from the rpmsg tree. > > > > This should have been fixed during the merge of the remoteproc tree > > since it happened after the clockevents tree merge; however, it does not > > look like my email was noticed by either maintainer and I did not pay > > attention when the pull was sent since I was on CC. > > Thanks, I've taken this patch directly into my tree since it was my > merge that screwed up. > Thanks Nathan, Suman and Linus.