All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Cameron <Jonathan.Cameron@Huawei.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Saravanan Sekar <sravanhome@gmail.com>,
	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 iio-fixes tree
Date: Mon, 31 Oct 2022 09:55:14 +0000	[thread overview]
Message-ID: <20221031095514.00003174@Huawei.com> (raw)
In-Reply-To: <20221031074006.1ca60136@canb.auug.org.au>

On Mon, 31 Oct 2022 07:40:06 +1100
Stephen Rothwell <sfr@canb.auug.org.au> wrote:

> Hi all,
> 
> In commit
> 
>   a589ef35fc62 ("iio: adc: mp2629: fix potential array out of bound
> access")
> 
> Fixes tag
> 
>   Fixes: 7abd9fb6468 ("iio: adc: mp2629: Add support for mp2629 ADC
> driver")
> 
> has these problem(s):
> 
>   - SHA1 should be at least 12 digits long
>     This can be fixed for the future 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").
> 

Doh, I clearly failed to run my local checks.  Will fix within next day
or so.

Thanks,

Jonathan

  reply	other threads:[~2022-10-31  9:55 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-30 20:40 linux-next: Fixes tag needs some work in the iio-fixes tree Stephen Rothwell
2022-10-31  9:55 ` Jonathan Cameron [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-04-29 22:26 Stephen Rothwell
2024-04-30 10:23 ` Jonathan Cameron
2024-06-02 22:44 Stephen Rothwell
2024-06-03  8:27 ` Jonathan Cameron

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=20221031095514.00003174@Huawei.com \
    --to=jonathan.cameron@huawei.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    --cc=sravanhome@gmail.com \
    /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.