All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sergey Shtylyov <s.shtylyov@omp.ru>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
	Wolfram Sang <wsa@the-dreams.de>
Cc: 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 i2c tree
Date: Wed, 18 Aug 2021 21:16:35 +0300	[thread overview]
Message-ID: <23d4fdb5-4a20-8d44-b98e-8b334bd2cdae@omp.ru> (raw)
In-Reply-To: <20210818075250.08a593f1@canb.auug.org.au>

On 8/18/21 12:52 AM, Stephen Rothwell wrote:

> In commit
> 
>   eef7fa1001c0 ("i2c: iop3xx: fix deferred probing")
> 
> Fixes tag
> 
>   Fixes: 489447380a29 ("handle errors returned by platform_get_irq*()")
> 
> has these problem(s):
> 
>   - Subject does not match target commit subject
>     Just use
> 	git log -1 --format='Fixes: %h ("%s")'
> 
> So:
> 
> Fixes: 489447380a29 ("[PATCH] handle errors returned by platform_get_irq*()")

   In this case I was innocent, I guess something ate [PATCH] on Wolfram's side. :-)

MBR, Sergei

  reply	other threads:[~2021-08-18 18:16 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-17 21:52 linux-next: Fixes tag needs some work in the i2c tree Stephen Rothwell
2021-08-18 18:16 ` Sergey Shtylyov [this message]
2021-08-19 17:15   ` Wolfram Sang
  -- strict thread matches above, loose matches on Subject: below --
2021-08-25 21:44 Stephen Rothwell
2021-08-17 21:49 Stephen Rothwell
2021-08-18 17:28 ` Sergey Shtylyov
2021-08-19 17:15   ` Wolfram Sang
2020-04-27 22:28 Stephen Rothwell
2020-04-28  7:01 ` Wolfram Sang
2020-04-28  8:41   ` Stephen Rothwell
2020-04-28 10:14     ` Wolfram Sang
2019-10-24 20:07 Stephen Rothwell
2019-08-01 14:02 Stephen Rothwell
2019-08-01 20:21 ` Wolfram Sang
2019-04-23 21:55 Stephen Rothwell
2019-04-23 22:17 ` Wolfram Sang

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=23d4fdb5-4a20-8d44-b98e-8b334bd2cdae@omp.ru \
    --to=s.shtylyov@omp.ru \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    --cc=wsa@the-dreams.de \
    /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.