public inbox for linux-next@vger.kernel.org
 help / color / mirror / Atom feed
From: Vineet Gupta <vgupta@kernel.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
	Vineet Gupta <vgupta@kernel.org>
Cc: Rolf Eike Beer <eb@emlix.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 arc-current tree
Date: Tue, 19 Apr 2022 09:47:08 -0700	[thread overview]
Message-ID: <a789eb92-7d4c-7ec5-8f3e-7765c238cb1f@kernel.org> (raw)
In-Reply-To: <20220419064023.4cedc139@canb.auug.org.au>

Hi Stephen,

On 4/18/22 13:40, Stephen Rothwell wrote:
> Hi all,
>
> In commit
>
>    a20aadab6ad6 ("arc: drop definitions of pgd_index() and pgd_offset{, _k}() entirely")
>
> Fixes tag
>
>    Fixes: 974b9b2c68f ("mm: consolidate pte_index() and pte_offset_*() definitions")
>
> 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").

I've fixed this and pushed.

Thx,
-Vineet

  reply	other threads:[~2022-04-19 16:48 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-18 20:40 linux-next: Fixes tag needs some work in the arc-current tree Stephen Rothwell
2022-04-19 16:47 ` Vineet Gupta [this message]
  -- strict thread matches above, loose matches on Subject: below --
2020-09-01  8:49 Stephen Rothwell
2020-09-01  9:13 ` Mike Rapoport
2020-09-01 11:36   ` Stephen Rothwell
2020-09-01 18:25     ` Vineet Gupta
2019-01-17 20:56 Stephen Rothwell
2019-01-17 20:32 Stephen Rothwell
2019-01-17 20:52 ` Vineet Gupta

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=a789eb92-7d4c-7ec5-8f3e-7765c238cb1f@kernel.org \
    --to=vgupta@kernel.org \
    --cc=eb@emlix.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox