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 Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 6DB40C433EF for ; Thu, 14 Apr 2022 08:46:36 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S241113AbiDNIs6 (ORCPT ); Thu, 14 Apr 2022 04:48:58 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:52662 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S236287AbiDNIsx (ORCPT ); Thu, 14 Apr 2022 04:48:53 -0400 Received: from muru.com (muru.com [72.249.23.125]) by lindbergh.monkeyblade.net (Postfix) with ESMTP id 46EA065D0B; Thu, 14 Apr 2022 01:46:29 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by muru.com (Postfix) with ESMTPS id 39BB280A4; Thu, 14 Apr 2022 08:43:51 +0000 (UTC) Date: Thu, 14 Apr 2022 11:46:26 +0300 From: Tony Lindgren To: "H. Nikolaus Schaller" Cc: Stephen Rothwell , Linux Kernel Mailing List , Linux Next Mailing List Subject: Re: linux-next: Fixes tag needs some work in the omap-fixes tree Message-ID: References: <20220413070201.248a9b11@canb.auug.org.au> <773CBF24-F8B7-481F-BBCE-53C13198FBED@goldelico.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <773CBF24-F8B7-481F-BBCE-53C13198FBED@goldelico.com> Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org * H. Nikolaus Schaller [220413 06:19]: > Hi Stephen, > > > Am 12.04.2022 um 23:02 schrieb Stephen Rothwell : > > > > Hi all, > > > > In commit > > > > 9be24a73de12 ("ARM: dts: Fix mmc order for omap3-gta04") > > > > Fixes tag > > > > Fixes: commit a1ebdb374199 ("ARM: dts: Fix swapped mmc order for omap3") > > > > has these problem(s): > > > > - leading word 'commit' unexpected > > Ah, I see. > Diff of patch is good but the commit message needs editing. > > What is the procedure to fix this case? Thanks for catching this, no need to do anything. I've fixed it up and pushed out an updated fixes branch. Regards, TOny