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>,
	Srinivas Neeli <srinivas.neeli@xilinx•com>,
	Marc Kleine-Budde <mkl@pengutronix•de>,
	Appana Durga Kedareswara rao <appana.durga.rao@xilinx•com>,
	Michal Simek <michal.simek@xilinx•com>,
	Venkatesh Yadav Abbarapu <venkatesh.abbarapu@xilinx•com>
Subject: linux-next: Fixes tags need some work in the net-next tree
Date: Fri, 16 Aug 2019 07:51:14 +1000	[thread overview]
Message-ID: <20190816075114.47adad49@canb.auug.org.au> (raw)

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

Hi all,

In commit

  3e994ff28f86 ("can: xilinx_can: xcan_set_bittiming(): fix the data phase btr1 calculation")

Fixes tag

  Fixes: c223da6 ("can: xilinx_can: Add support for CANFD FD frames")

has these problem(s):

  - SHA1 should be at least 12 digits long
    Can be fixed by setting core.abbrev to 12 (or more) or (for git v2.11
    or later) just making sure it is not set (or set to "auto").

In commit

  9d06bcb9aa48 ("can: xilinx_can: xcan_rx_fifo_get_next_frame(): fix FSR register FL and RI mask values for canfd 2.0")

Fixes tag

  Fixes: c223da6 ("can: xilinx_can: Add support for CANFD FD frames")

has these problem(s):

  - SHA1 should be at least 12 digits long
    Can be fixed by setting core.abbrev to 12 (or more) or (for git v2.11
    or later) just making sure it is not set (or set to "auto").

In commit

  e6997dd26884 ("can: xilinx_can: fix the data update logic for CANFD FD frames")

Fixes tag

  Fixes: c223da6 ("can: xilinx_can: Add support for CANFD FD frames")

has these problem(s):

  - SHA1 should be at least 12 digits long
    Can be fixed by setting core.abbrev to 12 (or more) or (for git v2.11
    or later) just making sure it is not set (or set to "auto").

In commit

  93bbd6c5eeb1 ("can: xilinx_can: xcanfd_rx(): fix FSR register handling in the RX path")

Fixes tag

  Fixes: c223da6 ("can: xilinx_can: Add support for CANFD FD frames")

has these problem(s):

  - SHA1 should be at least 12 digits long
    Can be fixed by setting core.abbrev to 12 (or more) or (for git v2.11
    or later) just making sure it is not set (or set to "auto").

In commit

  6b0d35891c83 ("can: xilinx_can: xcan_probe(): skip error message on deferred probe")

Fixes tag

  Fixes: b1201e44 ("can: xilinx CAN controller support")

has these problem(s):

  - SHA1 should be at least 12 digits long
    Can be fixed by setting core.abbrev to 12 (or more) or (for git v2.11
    or later) just making sure it is not set (or set to "auto").

-- 
Cheers,
Stephen Rothwell

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

             reply	other threads:[~2019-08-15 21:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-15 21:51 Stephen Rothwell [this message]
  -- strict thread matches above, loose matches on Subject: below --
2019-04-08 22:00 linux-next: Fixes tags need some work in the net-next tree Stephen Rothwell
2019-02-21 11:11 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=20190816075114.47adad49@canb.auug.org.au \
    --to=sfr@canb$(echo .)auug.org.au \
    --cc=appana.durga.rao@xilinx$(echo .)com \
    --cc=davem@davemloft$(echo .)net \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=michal.simek@xilinx$(echo .)com \
    --cc=mkl@pengutronix$(echo .)de \
    --cc=netdev@vger$(echo .)kernel.org \
    --cc=srinivas.neeli@xilinx$(echo .)com \
    --cc=venkatesh.abbarapu@xilinx$(echo .)com \
    /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