From: Lee Jones <lee.jones@linaro.org>
To: Greg KH <greg@kroah.com>
Cc: stable@vger.kernel.org
Subject: Re: [PATCH 4.19 3/3] ocfs2: remove ocfs2_is_o2cb_active()
Date: Tue, 26 Nov 2019 16:28:40 +0000 [thread overview]
Message-ID: <20191126162840.GK3296@dell> (raw)
In-Reply-To: <20191126162416.GA1657337@kroah.com>
On Tue, 26 Nov 2019, Greg KH wrote:
> On Tue, Nov 26, 2019 at 01:47:41PM +0000, Lee Jones wrote:
> > From: Gang He <ghe@suse.com>
> >
> > [ Upstream commit 9d452c602f0558ec3b0aeab1040bdf4dfbc590eb ]
>
> That's not a valid git commit id in Linus's tree :(
That's odd. I'll check my scripts.
They are new and you are the victim of the first run!
> These series are a mess. Can you redo them all and resend them so that
> I can apply them, and so I know what branch to apply them to? :)
I can do that.
--
Lee Jones [李琼斯]
Linaro Services Technical Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
next prev parent reply other threads:[~2019-11-26 16:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-26 13:47 [PATCH 4.19 1/3] ARM: 8904/1: skip nomap memblocks while finding the lowmem/highmem boundary Lee Jones
2019-11-26 13:47 ` [PATCH 4.19 2/3] media: siano: Use kmemdup instead of duplicating its function Lee Jones
2019-11-26 13:47 ` [PATCH 4.19 3/3] ocfs2: remove ocfs2_is_o2cb_active() Lee Jones
2019-11-26 16:24 ` Greg KH
2019-11-26 16:28 ` Lee Jones [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-11-27 7:22 [PATCH 4.19 1/3] ARM: 8904/1: skip nomap memblocks while finding the lowmem/highmem boundary Lee Jones
2019-11-27 7:22 ` [PATCH 4.19 3/3] ocfs2: remove ocfs2_is_o2cb_active() Lee Jones
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=20191126162840.GK3296@dell \
--to=lee.jones@linaro.org \
--cc=greg@kroah.com \
--cc=stable@vger.kernel.org \
/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