linux-mtd.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Artem Bityutskiy <dedekind1@gmail.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Richard Weinberger <richard@nod.at>,
	linux-mtd <linux-mtd@lists.infradead.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: [GIT PULL] UBI fixes for 4.0-rc5
Date: Fri, 20 Mar 2015 09:36:32 +0200	[thread overview]
Message-ID: <1426836992.8234.24.camel@sauron.fi.intel.com> (raw)

Hi Linus,

a pull request follows, but first a short explanation.

This pull request is based on a "random" commit, unfortunately. We
usually use a tagged -rc commit as a base, but not this time. Sorry for
this. Richard Weinberger is the new co-maintainer for UBI, and he was a
little bit too fast and did not wait for -rc1.


The following changes since commit 3d883483dc0a7261d73d8b1857a7387a1dd99eee:

  Merge branch 'fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/evalenti/linux-soc-thermal (2015-02-19 17:51:22 -0800)

are available in the git repository at:

  git://git.infradead.org/linux-ubifs.git tags/upstream-4.0-rc5

for you to fetch changes up to b388e6a7a6ba988998ddd83919ae8d3debf1a13d:

  UBI: fix missing brace control flow (2015-02-23 22:17:24 +0100)

----------------------------------------------------------------
This pull request fixes a bug introduced during the v4.0 merge window where we
forgot to put braces where they should be.

----------------------------------------------------------------
Brian Norris (1):
      UBI: fix missing brace control flow

 drivers/mtd/ubi/eba.c | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)


--
Regards,
Artem.

                 reply	other threads:[~2015-03-20  7:37 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=1426836992.8234.24.camel@sauron.fi.intel.com \
    --to=dedekind1@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=richard@nod.at \
    --cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).