From: Al Viro <viro@ZenIV.linux.org.uk>
To: Boaz Harrosh <bharrosh@panasas.com>
Cc: Randy Dunlap <randy.dunlap@oracle.com>, linux-scsi@vger.kernel.org
Subject: Re: [PATCH -next] osd_uld: fix printk format warning
Date: Mon, 4 May 2009 19:30:55 +0100 [thread overview]
Message-ID: <20090504183055.GI8633@ZenIV.linux.org.uk> (raw)
In-Reply-To: <49FF133D.9020603@panasas.com>
On Mon, May 04, 2009 at 07:09:33PM +0300, Boaz Harrosh wrote:
> Thanks Al, very much. It is exactly what I was hoping for, but could not
> figure out for myself.
>
> I will give it an hard testing ASAP, and will queue it for next kernel (2.6.31).
>
> Can I take the osd cleanup hunk form your patchset + Randy's fix and serialize them
> together with this through the scsi tree? (Together with the rest of the osd patches)
> Is your patchset dependent on the osd bit for removal of some code? If so then I'll
> send this patch through your tree so not to have conflicts in linux-next.
Actually, git should manage such merge just fine, so -next is probably not
a concern. In any case, if there are any problems with the merge I can
take that chunk out - nothing depends on it yet in the public queue. Or
I could take this incremental in vfs tree - also not a problem...
next prev parent reply other threads:[~2009-05-04 18:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20090429092631.a76e79c5.randy.dunlap@oracle.com>
2009-04-29 18:51 ` [PATCH -next] osd_uld: fix printk format warning Al Viro
2009-04-30 10:30 ` Boaz Harrosh
2009-05-03 18:35 ` Al Viro
2009-05-03 19:02 ` Al Viro
2009-05-04 16:09 ` Boaz Harrosh
2009-05-04 18:30 ` Al Viro [this message]
2009-04-23 21:57 Randy Dunlap
2009-04-26 15:32 ` 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=20090504183055.GI8633@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=bharrosh@panasas.com \
--cc=linux-scsi@vger.kernel.org \
--cc=randy.dunlap@oracle.com \
/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.