linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jan Kara <jack@suse.cz>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Jan Kara <jack@suse.cz>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Randy Dunlap <randy.dunlap@oracle.com>
Subject: Please pull UDF updates for 2.6.34-rc1
Date: Thu, 11 Mar 2010 16:08:51 +0100	[thread overview]
Message-ID: <20100311150851.GD4245@quack.suse.cz> (raw)
In-Reply-To: <20100309091313.c568ef5a.randy.dunlap@oracle.com>

On Tue 09-03-10 09:13:13, Randy Dunlap wrote:
> On Tue, 9 Mar 2010 17:28:04 +0100 Jan Kara wrote:
> > > It's out there now. I still have a few trees I already got pull requests 
> > > for, and that I want to look over a bit more (ceph, gdb tree etc), and 
> > > it's possible that I've just overlooked some other pull request.
> >   It seems you haven't pulled my UDF tree (requested on Thursday -
> > http://lkml.indiana.edu/hypermail/linux/kernel/1003.0/02186.html).
> >   I've rebased the tree on top of 2.6.34-rc1 so could you please pull
> > now?
> >   The full pull request for your convenience:
> > 
> >   could you please pull from
> > 
> > git://git.kernel.org/pub/scm/linux/kernel/git/jack/linux-udf-2.6.git for_linus
> > 
> >   to get:
> > 
> > Akinobu Mita (1):
> >       udf: use ext2_find_next_bit
> > 
> > Jan Kara (2):
> >       udf: Fix unalloc space handling in udf_update_inode
> >       udf: Do not read inode before writing it
> > 
> > The diffstat is
> > 
> >  fs/udf/balloc.c |   49 +------------------------------------------------
> >  fs/udf/inode.c  |   34 +++++++++++++++++-----------------
> >  2 files changed, 18 insertions(+), 65 deletions(-)
> 
> I have no objections, fwiw, but please change the $subject line...
  OK, changing the subject line to catch attention.

								Honza
-- 
Jan Kara <jack@suse.cz>
SUSE Labs, CR

      reply	other threads:[~2010-03-11 17:00 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-08 20:33 Linux 2.6.34-rc1 Linus Torvalds
2010-03-08 22:06 ` Jiri Slaby
2010-03-13 21:56   ` Writable limits (was Re: Linux 2.6.34-rc1) Jiri Kosina
2010-03-23 13:59     ` Pavel Machek
2010-03-09  2:14 ` Linux 2.6.34-rc1 Mike Frysinger
2010-03-09 16:28 ` Jan Kara
2010-03-09 17:13   ` Randy Dunlap
2010-03-11 15:08     ` Jan Kara [this message]

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=20100311150851.GD4245@quack.suse.cz \
    --to=jack@suse.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=randy.dunlap@oracle.com \
    --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).