All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Wolfram Sang <wsa@the-dreams.de>
Cc: "Linux Next Mailing List" <linux-next@vger.kernel.org>,
	"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
	"Michał Mirosław" <mirq-linux@rere.qmqm.pl>
Subject: linux-next: Fixes tag needs some work in the i2c tree
Date: Fri, 2 Aug 2019 00:02:52 +1000	[thread overview]
Message-ID: <20190802000252.74ada349@canb.auug.org.au> (raw)

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

Hi all,

In commit

  9c5718e14b81 ("i2c: at91: disable TXRDY interrupt after sending data")

Fixes tag

  Fixes: fac368a0404 ("i2c: at91: add new driver")

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-01 14:02 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-01 14:02 Stephen Rothwell [this message]
2019-08-01 20:21 ` linux-next: Fixes tag needs some work in the i2c tree Wolfram Sang
  -- strict thread matches above, loose matches on Subject: below --
2021-08-25 21:44 Stephen Rothwell
2021-08-17 21:52 Stephen Rothwell
2021-08-18 18:16 ` Sergey Shtylyov
2021-08-19 17:15   ` Wolfram Sang
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-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=20190802000252.74ada349@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=mirq-linux@rere.qmqm.pl \
    --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.