public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Christoph Fritz <chf.fritz@googlemail.com>
To: Ben Hutchings <ben@decadent.org.uk>
Cc: Artem Bityutskiy <artem.bityutskiy@linux.intel.com>,
	linux-mtd@lists.infradead.org, Al Viro <viro@zeniv.linux.org.uk>,
	stable@vger.kernel.org
Subject: Add "UBIFS: fix a horrid bug" to 3.2 branch?
Date: Mon, 08 Jul 2013 11:15:54 +0200	[thread overview]
Message-ID: <1373274954.4186.38.camel@mars> (raw)

Hi Ben,

 I can't find an incarnation of commit "UBIFS: fix a horrid
bug" (605c912) in current stable branch 3.2 but 3.0, 3.4, 3.9 and
current.

Are there any concerns adding these commits:

    UBIFS: prepare to fix a horrid bug
    UBIFS: fix a horrid bug

Thanks
 -- Christoph

             reply	other threads:[~2013-07-08  9:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-08  9:15 Christoph Fritz [this message]
2013-07-24  2:55 ` Add "UBIFS: fix a horrid bug" to 3.2 branch? Ben Hutchings

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=1373274954.4186.38.camel@mars \
    --to=chf.fritz@googlemail.com \
    --cc=artem.bityutskiy@linux.intel.com \
    --cc=ben@decadent.org.uk \
    --cc=linux-mtd@lists.infradead.org \
    --cc=stable@vger.kernel.org \
    --cc=viro@zeniv.linux.org.uk \
    /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