From: Jan Kara <jack@suse.cz>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PATCH] UDF fix for 2.6.27-rc5
Date: Wed, 10 Sep 2008 23:15:07 +0200 [thread overview]
Message-ID: <20080910211507.GA21384@duck.suse.cz> (raw)
In-Reply-To: <alpine.LFD.1.10.0809101105240.3384@nehalem.linux-foundation.org>
On Wed 10-09-08 11:06:35, Linus Torvalds wrote:
> On Wed, 10 Sep 2008, Jan Kara wrote:
> >
> > would you please pull from
> >
> > git://git.kernel.org/pub/scm/linux/kernel/git/jack/linux-udf-2.6.git for_linus
> >
> > to get the following fix:
> >
> > Christoph Hellwig (1):
> > udf: add llseek method
> >
> > fs/udf/file.c | 1 +
> > 1 files changed, 1 insertions(+), 0 deletions(-)
>
> This is not AT ALL what I get when I pull. I get
>
> udf: Fix error paths in udf_new_inode()
> udf: Fix lock inversion between iprune_mutex and alloc_mutex (v2)
>
> which is
>
> fs/udf/ialloc.c | 44 +++++++++++++++++++-------------------------
> 1 files changed, 19 insertions(+), 25 deletions(-)
>
> Hmm?
Thanks for catching this. I managed to make two mistakes - first I forgot
to push changes to master.kernel.org and second I forgot to push older
changes to you after sending them for review to LKML. So a second try :).
Would you please pull
git://git.kernel.org/pub/scm/linux/kernel/git/jack/linux-udf-2.6.git for_linus
to get:
Christoph Hellwig (1):
udf: add llseek method
Jan Kara (2):
udf: Fix lock inversion between iprune_mutex and alloc_mutex (v2)
udf: Fix error paths in udf_new_inode()
The diffstat is:
fs/udf/file.c | 1 +
fs/udf/ialloc.c | 44 +++++++++++++++++++-------------------------
2 files changed, 20 insertions(+), 25 deletions(-)
Thanks.
Honza
--
Jan Kara <jack@suse.cz>
SUSE Labs, CR
prev parent reply other threads:[~2008-09-10 21:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-10 9:06 Jan Kara
2008-09-10 18:06 ` Linus Torvalds
2008-09-10 21:15 ` 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=20080910211507.GA21384@duck.suse.cz \
--to=jack@suse.cz \
--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
all inboxes | Powered by JetHome®