public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Artem Bityutskiy <Artem.Bityutskiy@nokia.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Artem Bityutskiy <Artem.Bityutskiy@nokia.com>,
	linux-kernel@vger.kernel.org
Subject: [GIT PULL] More UBI/UBIFS changes for 2.6.39
Date: Thu, 24 Mar 2011 16:38:35 +0200	[thread overview]
Message-ID: <20110324143835.29758.362.sendpatchset@localhost.localdomain> (raw)

Hi Linus,

I've found a couple of brown-paperbag bugs in my changes which
you have merged this merge window. Also, we've fixed one UBIFS
assertion warning and I forgot to kill one Kconfig option.

So I've composed another UBI/UBIFS pull request where I address
the issues introduced in the previous pull request. I did not find
better way than to base the pull request on top of a "random"
current commit, hopefully this is acceptable. Yes, I tested the
patches with 2.6.38 release, not this commit.

Please, pull.

The following changes since commit 4bbba111d94781d34081c37856bbc5eb33f6c72a:

  Merge branch 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound-2.6 (2011-03-23 07:58:09 -0700)

are available in the git repository at:

  git://git.infradead.org/ubi-2.6.git for-linus

Artem Bityutskiy (4):
      UBI: use GFP_NOFS properly
      UBIFS: use GFP_NOFS properly
      UBIFS: kill CONFIG_UBIFS_FS_DEBUG_CHKS
      UBIFS: fix assertion warning and refine comments

 drivers/mtd/ubi/io.c  |    4 ++--
 fs/ubifs/Kconfig      |    9 ---------
 fs/ubifs/debug.c      |    2 +-
 fs/ubifs/file.c       |   11 +++++++----
 fs/ubifs/lprops.c     |    2 +-
 fs/ubifs/lpt_commit.c |    4 ++--
 fs/ubifs/orphan.c     |    2 +-
 7 files changed, 14 insertions(+), 20 deletions(-)


Thanks,
Artem.

                 reply	other threads:[~2011-03-24 14:35 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=20110324143835.29758.362.sendpatchset@localhost.localdomain \
    --to=artem.bityutskiy@nokia.com \
    --cc=linux-kernel@vger.kernel.org \
    --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