From: Greg KH <gregkh@linuxfoundation.org>
To: Richard Weinberger <richard@nod.at>
Cc: stable@vger.kernel.org
Subject: Re: [PATCH 0/6] UBI fixes backported to 4.4.x
Date: Mon, 23 Jul 2018 14:20:49 +0200 [thread overview]
Message-ID: <20180723122049.GB14445@kroah.com> (raw)
In-Reply-To: <20180723121014.30778-1-richard@nod.at>
On Mon, Jul 23, 2018 at 02:10:08PM +0200, Richard Weinberger wrote:
> Greg,
>
> this series contains backports of the following upstream commits:
>
> 243a4f8126fc ubi: Introduce vol_ignored()
> fdf10ed710c0 ubi: Rework Fastmap attach base code
> 74f2c6e9a47c ubi: Be more paranoid while seaching for the most recent Fastmap
> 2e8f08deabbc ubi: Fix races around ubi_refill_pools()
> f7d11b33d4e8 ubi: Fix Fastmap's update_vol()
> 5793f39de7f6 ubi: fastmap: Erase outdated anchor PEBs during attach
This last one was really commit f78e5623f45bab2b726eec29dc5cefbbab2d0b1c
upstream, please be a bit more careful in the future.
All now queued up.
thanks,
greg k-h
next prev parent reply other threads:[~2018-07-23 13:21 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-23 12:10 [PATCH 0/6] UBI fixes backported to 4.4.x Richard Weinberger
2018-07-23 12:10 ` [PATCH 1/6] ubi: Introduce vol_ignored() Richard Weinberger
2018-07-23 12:16 ` Greg KH
2018-07-23 12:10 ` [PATCH 2/6] ubi: Rework Fastmap attach base code Richard Weinberger
2018-07-23 12:10 ` [PATCH 3/6] ubi: Be more paranoid while seaching for the most recent Fastmap Richard Weinberger
2018-07-23 12:10 ` [PATCH 4/6] ubi: Fix races around ubi_refill_pools() Richard Weinberger
2018-07-23 12:10 ` [PATCH 5/6] ubi: Fix Fastmap's update_vol() Richard Weinberger
2018-07-23 12:10 ` [PATCH 6/6] ubi: fastmap: Erase outdated anchor PEBs during attach Richard Weinberger
2018-07-23 12:20 ` Greg KH [this message]
2018-07-23 12:43 ` [PATCH 0/6] UBI fixes backported to 4.4.x Richard Weinberger
2018-07-23 12:50 ` Greg KH
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=20180723122049.GB14445@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=richard@nod.at \
--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 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.