All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Wim Van Sebroeck <wim@iguana.be>
Cc: Sam Protsenko <semen.protsenko@linaro.org>,
	Andrej Picej <andrej.picej@norik.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: linux-next: Fixes tags need some work in the watchdog tree
Date: Tue, 4 Jan 2022 08:36:59 +1100	[thread overview]
Message-ID: <20220104083659.4e5f2754@canb.auug.org.au> (raw)

[-- Attachment #1: Type: text/plain, Size: 728 bytes --]

Hi all,

In commit

  02d04e694fa3 ("watchdog: s3c2410: Fix getting the optional clock")

Fixes tag

  Fixes: a4f3dc8d5fbc ("watchdog: s3c2410: Support separate source clock")

has these problem(s):

  - Target SHA1 does not exist

Maybe you meant

Fixes: e249d01b5e8b ("watchdog: s3c2410: Support separate source clock")

In commit

  ce3401c72f01 ("watchdog: da9063: Add hard dependency on I2C")

Fixes tag

  Fixes: 5ea29919c294 ("watchdog: da9063: use atomic safe i2c transfer in reset handler")

has these problem(s):

  - Target SHA1 does not exist

Maybe you meant

Fixes: 968011a291f3 ("watchdog: da9063: use atomic safe i2c transfer in reset handler")

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

             reply	other threads:[~2022-01-03 21:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-03 21:36 Stephen Rothwell [this message]
2022-01-04  8:06 ` linux-next: Fixes tags need some work in the watchdog tree Andrej Picej
2022-01-05 10:43   ` Wim Van Sebroeck

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=20220104083659.4e5f2754@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=andrej.picej@norik.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=semen.protsenko@linaro.org \
    --cc=wim@iguana.be \
    /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.