All of lore.kernel.org
 help / color / mirror / Atom feed
From: Namhyung Kim <namhyung@gmail.com>
To: Laurent Vivier <Laurent.Vivier@bull.net>
Cc: Jens Axboe <jaxboe@fusionio.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2/2] loop: handle on-demand devices correctly
Date: Wed, 25 May 2011 00:08:03 +0900	[thread overview]
Message-ID: <1306249683.1751.12.camel@leonhard> (raw)
In-Reply-To: <1306249314.2838.19.camel@b015126-ux.fr.ad.bull.net>

2011-05-24 (화), 17:01 +0200, Laurent Vivier:
> Le mardi 24 mai 2011 à 23:57 +0900, Namhyung Kim a écrit :
> > 2011-05-24 (화), 16:45 +0200, Jens Axboe:
> > > Thanks, applied. Seems we should mark this for stable.
> > > 
> > 
> > Hi Jens,
> > 
> > The partition handling was introduced by commit 476a4813cfdd ("loop:
> > manage partitions in disk image") so that we need these patches for all
> > stable releases, AFAICS.
> > 
> > $ git name-rev --tags 476a4813cfdd
> > 476a4813cfdd tags/v2.6.26-rc1~1115^2~9
> > 
> > Now I can see that brd (ramdisk) module seems to have same problems with
> > loop. I'll work on that, too.
> 
> Have a look to nbd.c too.
> 
> Regards,
> Laurent
> 

Hi Laurent,

I'll take a look on that too after looking at brd. Thanks for the
comment.


-- 
Regards,
Namhyung Kim



  reply	other threads:[~2011-05-24 15:08 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-24 14:36 [PATCH 1/2] loop: limit 'max_part' module param to DISK_MAX_PARTS Namhyung Kim
2011-05-24 14:36 ` [PATCH 2/2] loop: handle on-demand devices correctly Namhyung Kim
2011-05-24 14:45   ` Jens Axboe
2011-05-24 14:57     ` Namhyung Kim
2011-05-24 15:00       ` Jens Axboe
2011-05-24 15:01       ` Laurent Vivier
2011-05-24 15:08         ` Namhyung Kim [this message]
2011-05-24 14:46 ` [PATCH 1/2] loop: limit 'max_part' module param to DISK_MAX_PARTS Jens Axboe
2011-05-24 15:05 ` Laurent Vivier

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=1306249683.1751.12.camel@leonhard \
    --to=namhyung@gmail.com \
    --cc=Laurent.Vivier@bull.net \
    --cc=jaxboe@fusionio.com \
    --cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.