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.2 required=3.0 tests=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 1D30BC432C0 for ; Thu, 21 Nov 2019 15:15:19 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id E8909206F4 for ; Thu, 21 Nov 2019 15:15:18 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726379AbfKUPPS (ORCPT ); Thu, 21 Nov 2019 10:15:18 -0500 Received: from muru.com ([72.249.23.125]:43130 "EHLO muru.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726358AbfKUPPS (ORCPT ); Thu, 21 Nov 2019 10:15:18 -0500 Received: from atomide.com (localhost [127.0.0.1]) by muru.com (Postfix) with ESMTPS id B1C4980DB; Thu, 21 Nov 2019 15:15:54 +0000 (UTC) Date: Thu, 21 Nov 2019 07:15:14 -0800 From: Tony Lindgren To: Stephen Rothwell Cc: Linux Next Mailing List , Linux Kernel Mailing List , Grygorii Strashko Subject: Re: linux-next: Fixes tag needs some work in the omap tree Message-ID: <20191121151514.GV35479@atomide.com> References: <20191121072254.79e13f56@canb.auug.org.au> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20191121072254.79e13f56@canb.auug.org.au> User-Agent: Mutt/1.12.2 (2019-09-21) Sender: linux-next-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-next@vger.kernel.org * Stephen Rothwell [191120 21:01]: > Hi all, > > In commit > > e130d53f2599 ("ARM: dts: dra7: fix cpsw mdio fck clock") > > Fixes tag > > Fixes: commit 1faa415c9c6e ("ARM: dts: Add fck for cpsw mdio for omap variants") > > has these problem(s): > > - leading word 'commit' unexpected Thanks I'll fix this in omap-for-v5.5/dt-v2 branch. Regards, Tony