All of lore.kernel.org
 help / color / mirror / Atom feed
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
Date: Thu, 14 Apr 2022 11:46:26 +0300	[thread overview]
Message-ID: <YlffYlfFuH6ur7GP@atomide.com> (raw)
In-Reply-To: <773CBF24-F8B7-481F-BBCE-53C13198FBED@goldelico.com>

* 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

  reply	other threads:[~2022-04-14  8:46 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-12 21:02 linux-next: Fixes tag needs some work in the omap-fixes tree Stephen Rothwell
2022-04-13  6:21 ` H. Nikolaus Schaller
2022-04-14  8:46   ` Tony Lindgren [this message]
  -- strict thread matches above, loose matches on Subject: below --
2020-11-10 21:16 Stephen Rothwell
2020-11-11  7:21 ` Tony Lindgren
2019-12-17 20:13 Stephen Rothwell
2019-12-17 23:23 ` Tony Lindgren
2019-09-10 14:08 Stephen Rothwell
2019-09-10 14:32 ` Tony Lindgren
2019-01-23  5:32 Stephen Rothwell
2019-01-23 21:14 ` Tony Lindgren

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=YlffYlfFuH6ur7GP@atomide.com \
    --to=tony@atomide.com \
    --cc=hns@goldelico.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.