public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Richard Weinberger <richard@nod.at>
To: Martin Lund <martin.lund@keep-it-simple.com>
Cc: takei744@oki.com, linux-mtd@lists.infradead.org
Subject: Re: Questions about ubifs,ubi and mtd?
Date: Thu, 13 Dec 2018 12:38:27 +0100	[thread overview]
Message-ID: <3057355.peyXOFjNrj@blindfold> (raw)
In-Reply-To: <CAB7pii3ayyPK=trs=wV_Egs+Lt1GMMeh_g_=D82MNefgqqE00A@mail.gmail.com>

Martin,

Am Donnerstag, 13. Dezember 2018, 12:32:43 CET schrieb Martin Lund:
> On Thu, Dec 13, 2018 at 11:45 AM 武井 克明 <takei744@oki.com> wrote:
> >
> > Dear Richard,
> >
> > We appreciate your precious advice.
> > We understood the quality status of kernel 3.2.26.
> > From now on, we would like to backport from the latest UBI and UBIFS.
> > Do you think that it is enough to backport the next part?
> >  - drivers/mtd
> >  - drivers/mtd/ubi
> >  - fs/ubifs
> >
> 
> I recommend you first take a close look at the git history of Linux
> 3.2.26 and onward to see if there are any immediate UBI/UBIFS fixes
> available that might relate/solve the issue you are seeing. It might
> be an easier path than jumping into a big task like back porting
> latest UBI/UBIFS to such an old kernel.

Given the age of this kernel it will be massive pain in any case.
Digging through the history, identifying and backporting fixes sounds
more easier than it actually is.
Small fixes often depend on larger patches which are hard to apply
to old kernels.

Thanks,
//richard 

  reply	other threads:[~2018-12-13 11:38 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-11 14:08 Questions about ubifs,ubi and mtd? 武井 克明
2018-12-11 17:10 ` Richard Weinberger
2018-12-12  1:07   ` 武井 克明
2018-12-12  9:20     ` Richard Weinberger
2018-12-13 10:45       ` 武井 克明
2018-12-13 11:32         ` Martin Lund
2018-12-13 11:38           ` Richard Weinberger [this message]
2018-12-13 12:04             ` 武井 克明
2018-12-13 11:35         ` Richard Weinberger
2018-12-13 17:18           ` Steve deRosier
2018-12-13 21:16             ` Richard Weinberger
2018-12-13 22:22               ` Steve deRosier
2018-12-15 11:24                 ` Miquel Raynal
2018-12-14  6:18               ` Katsuaki Takei/OKI/JP
2018-12-14  6:11             ` Katsuaki Takei/OKI/JP

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=3057355.peyXOFjNrj@blindfold \
    --to=richard@nod.at \
    --cc=linux-mtd@lists.infradead.org \
    --cc=martin.lund@keep-it-simple.com \
    --cc=takei744@oki.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox