linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kari Argillander <kari.argillander@gmail.com>
To: Konstantin Komarov <almaz.alexandrovich@paragon-software.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	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 ntfs3 tree
Date: Tue, 21 Sep 2021 17:29:19 +0300	[thread overview]
Message-ID: <20210921142919.ahfrtqcu7lpenzsz@kari-VirtualBox> (raw)
In-Reply-To: <3320944d-8fac-0a22-ee38-f08974fcaed7@paragon-software.com>

On Tue, Sep 21, 2021 at 04:50:02PM +0300, Konstantin Komarov wrote:
> 
> 
> On 21.09.2021 01:31, Stephen Rothwell wrote:
> > Hi all,
> > 
> > In commit
> > 
> >   0412016e4807 ("fs/ntfs3: Fix wrong error message $Logfile -> $UpCase")
> > 
> > Fixes tag
> > 
> >   Fixes: 203c2b3a406a ("fs/ntfs3: Add initialization of super block")
> > 
> > has these problem(s):
> > 
> >   - Target SHA1 does not exist
> > 
> > Maybe you meant
> > 
> > Fixes: 82cae269cfa9 ("fs/ntfs3: Add initialization of super block")
> > 
> 
> Hello.
> 
> You are right, correct SHA is 82cae269cfa9.
> Sorry, I've missed this while applying patch.

Sorry also from my part.

> As far as I know there is no way to fix this now -
> commit is already in linux-next.

But these things needs fixing. Rebase is needed.


  reply	other threads:[~2021-09-21 14:29 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-20 22:31 linux-next: Fixes tag needs some work in the ntfs3 tree Stephen Rothwell
2021-09-21 13:50 ` Konstantin Komarov
2021-09-21 14:29   ` Kari Argillander [this message]
2021-09-26 21:47   ` Kari Argillander
2021-09-26 22:02     ` Stephen Rothwell
2022-11-13  9: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=20210921142919.ahfrtqcu7lpenzsz@kari-VirtualBox \
    --to=kari.argillander@gmail.com \
    --cc=almaz.alexandrovich@paragon-software.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;
as well as URLs for NNTP newsgroup(s).