From: James Bottomley <James.Bottomley@suse.de>
To: Boaz Harrosh <bharrosh@panasas.com>
Cc: open-osd <osd-dev@open-osd.org>,
Stephen Rothwell <sfr@canb.auug.org.au>,
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: Sun, 29 Nov 2009 10:23:35 -0500 [thread overview]
Message-ID: <1259508215.2827.15.camel@mulgrave.site> (raw)
In-Reply-To: <4B1283C9.1030002@panasas.com>
On Sun, 2009-11-29 at 16:23 +0200, Boaz Harrosh wrote:
> On 11/29/2009 03:46 PM, James Bottomley wrote:
> >>
> >> Should I repost the correct two patches (my preference)? should I send in a fix to
> >> current scsi-misc tree? or should I send two SQUASH-ME patches to the two bad commits
> >> in your tree?
> >>
> >> How do you want to proceed?
> >
> > Send me the replacement patch (and tell me which commit id in my tree
> > it's replacing).
> >
>
> Thank you James.
>
> I'm posting two patches as reply to this mail.
>
> [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).
James
next prev parent reply other threads:[~2009-11-29 15:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-27 3:32 linux-next: manual merge of the osd tree with the scsi tree 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 14:25 ` [PATCH 1/2] osduld: Use device->release instead of internal kref Boaz Harrosh
2009-11-29 14:26 ` [PATCH 2/2] libosd: osd_dev_info: Unique Identification of an OSD device Boaz Harrosh
2009-11-29 15:23 ` James Bottomley [this message]
2009-11-29 21:44 ` linux-next: manual merge of the osd tree with the scsi tree Stephen Rothwell
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=1259508215.2827.15.camel@mulgrave.site \
--to=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 \
--cc=sfr@canb.auug.org.au \
/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).