Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Date:   Thu, 14 Apr 2022 11:46:26 +0300
From:   Tony Lindgren <tony@atomide.com>
To:     "H. Nikolaus Schaller" <hns@goldelico.com>
Cc:     Stephen Rothwell <sfr@canb.auug.org.au>,
        Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
        Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: Fixes tag needs some work in the omap-fixes tree
Message-ID: <YlffYlfFuH6ur7GP@atomide.com>
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

* H. Nikolaus Schaller <hns@goldelico.com> [220413 06:19]:
> Hi Stephen,
> 
> > Am 12.04.2022 um 23:02 schrieb Stephen Rothwell <sfr@canb.auug.org.au>:
> > 
> > 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