public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb•auug.org.au>
To: David Miller <davem@davemloft•net>, Networking <netdev@vger•kernel.org>
Cc: Linux Next Mailing List <linux-next@vger•kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
	Dan Murphy <dmurphy@ti•com>
Subject: linux-next: Fixes tags need some work in the net tree
Date: Mon, 13 Jan 2020 06:50:54 +1100	[thread overview]
Message-ID: <20200113065054.25c85bac@canb.auug.org.au> (raw)

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

Hi all,

In commit

  a26ad4d5676f ("net: phy: DP83822: Update Kconfig with DP83825I support")

Fixes tag

  Fixes: 32b12dc8fde1  ("net: phy: Add DP83825I to the DP83822 driver")

has these problem(s):

  - Target SHA1 does not exist

Maybe you meant

Fixes: 06acc17a9621 ("net: phy: Add DP83825I to the DP83822 driver")

In commit

  443180567763 ("net: phy: DP83TC811: Fix typo in Kconfig")

Fixes tag

  Fixes: 6d749428788b {"net: phy: DP83TC811: Introduce support for the DP83TC811 phy")

has these problem(s):

  - Target SHA1 does not exist

Maybe you meant

Fixes: b753a9faaf9a ("net: phy: DP83TC811: Introduce support for the DP83TC811 phy")

-- 
Cheers,
Stephen Rothwell

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

             reply	other threads:[~2020-01-12 19:51 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-12 19:50 Stephen Rothwell [this message]
  -- strict thread matches above, loose matches on Subject: below --
2021-06-16 22:03 linux-next: Fixes tags need some work in the net tree Stephen Rothwell
2021-06-17  1:35 ` Joakim Zhang
2020-09-30 22:48 Stephen Rothwell
2019-05-08 21:43 Stephen Rothwell
2019-02-17 13:52 Stephen Rothwell
2019-01-29 20:49 Stephen Rothwell

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=20200113065054.25c85bac@canb.auug.org.au \
    --to=sfr@canb$(echo .)auug.org.au \
    --cc=davem@davemloft$(echo .)net \
    --cc=dmurphy@ti$(echo .)com \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=netdev@vger$(echo .)kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox