Linux SCSI subsystem development
 help / color / mirror / Atom feed
From: Boaz Harrosh <bharrosh@panasas.com>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	open-osd <osd-dev@open-osd.org>,
	linux-fsdevel <linux-fsdevel@vger.kernel.org>,
	linux-scsi <linux-scsi@vger.kernel.org>
Subject: Re: [GIT PULL] exofs: 3 changes to exofs & osd
Date: Tue, 18 Dec 2012 13:18:30 +0200	[thread overview]
Message-ID: <50D05106.5090200@panasas.com> (raw)
In-Reply-To: <1355828291.2630.21.camel@dabdike.int.hansenpartnership.com>

On 12/18/2012 12:58 PM, James Bottomley wrote:
> On Mon, 2012-12-17 at 18:53 +0200, Boaz Harrosh wrote:
>> Hi Linus.
>>
>> Please pull the following changes since commit [ddffeb8c] Linux 3.7-rc1
>> They are available in the git repository at:
>>
>>   git://git.open-osd.org/linux-open-osd.git for-linus
>>
>> for you to fetch changes up to
>> 	[861d6660] exofs: don't leak io_state and pages on read error (2012-12-14 12:17:32 +0200)
>>
>> These are just 3 patches, the last two are bug fixes on the error paths
>> in exofs.
>>
>> The important patch is the one to osd_uld which adds sysfs info to osd
>> devices for use by user-mode clustering discovery software. I'm already
>> sitting on this patch since before February this year, It is important for
>> some of the big installation cluster systems, who's been compiling their
>> own kernel just for that patch.
> 
> I'm a bit perplexed by this.  You got notice when it was added to the
> SCSI tree and now it's already upstream:
> 
> commit 51976a8c85cec0c62e410bc38b8a11dbc690764d
> Author: Boaz Harrosh <bharrosh@panasas.com>
> Date:   Wed Oct 24 14:51:41 2012 -0700
> 
>     [SCSI] osd_uld: Add osdname & systemid sysfs at scsi_osd class
> 
> But the authorship info differs ... it looks like you forgot to include
> the From: tag in your original patch send.
> 

I'm so sorry, I completely goofed on this one. It's what happens when
you are swamped with other work and are doing things without thinking.
I totally forgot that I need to remove this patch. 

Both these patches where in linux-next for a long time. So I believe
the merge will go just fine. Lets leave it like this, or I can rebase
and remove it?

> James
> 
> 

Thanks
Boaz


  reply	other threads:[~2012-12-18 11:18 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-17 16:53 [GIT PULL] exofs: 3 changes to exofs & osd Boaz Harrosh
2012-12-18 10:58 ` James Bottomley
2012-12-18 11:18   ` Boaz Harrosh [this message]
2012-12-18 11:28     ` James Bottomley
2012-12-18 11:35       ` Boaz Harrosh

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=50D05106.5090200@panasas.com \
    --to=bharrosh@panasas.com \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=osd-dev@open-osd.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