mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: James Bottomley <James.Bottomley@suse.de>
Cc: Boaz Harrosh <bharrosh@panasas.com>,
	open-osd <osd-dev@open-osd.org>,
	linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-scsi <linux-scsi@vger.kernel.org>
Subject: Re: linux-next: manual merge of the osd tree with the scsi tree
Date: Mon, 30 Nov 2009 08:44:00 +1100	[thread overview]
Message-ID: <20091130084400.adb3e293.sfr@canb.auug.org.au> (raw)
In-Reply-To: <1259508215.2827.15.camel@mulgrave.site>

[-- Attachment #1: Type: text/plain, Size: 691 bytes --]

Hi James, Boaz,

On Sun, 29 Nov 2009 10:23:35 -0500 James Bottomley <James.Bottomley@suse.de> wrote:
>
> > [PATCH 1/2] osduld: Use device->release instead of internal kref
> > which replaces:
> > f89b9ee [SCSI] osduld: Use device->release instead of internal kref
> > 
> > and
> > 
> > [PATCH 2/2] libosd: osd_dev_info: Unique Identification of an OSD device
> > which replaces:
> > 3b616d4 [SCSI] libosd: osd_dev_info: Unique Identification of an OSD device
> 
> OK, replacement should be done in scsi-misc (give an hour or two for
> mirror updates).

Thanks guys.
-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/

[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]

      reply	other threads:[~2009-11-29 21:43 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-27  3:32 Stephen Rothwell
2009-11-29  9:10 ` Boaz Harrosh
2009-11-29 13:07   ` Boaz Harrosh
2009-11-29 13:46     ` James Bottomley
2009-11-29 14:23       ` Boaz Harrosh
2009-11-29 15:23         ` James Bottomley
2009-11-29 21:44           ` Stephen Rothwell [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=20091130084400.adb3e293.sfr@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=James.Bottomley@suse.de \
    --cc=bharrosh@panasas.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=osd-dev@open-osd.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®