From: Boaz Harrosh <bharrosh@panasas.com>
To: Randy Dunlap <randy.dunlap@oracle.com>,
Al Viro <viro@zeniv.linux.org.uk>
Cc: scsi <linux-scsi@vger.kernel.org>,
James Bottomley <James.Bottomley@HansenPartnership.com>
Subject: Re: [PATCH -next] osd_uld: fix printk format warning
Date: Sun, 26 Apr 2009 18:32:57 +0300 [thread overview]
Message-ID: <49F47EA9.3070204@panasas.com> (raw)
In-Reply-To: <49F0E43B.80501@oracle.com>
On 04/24/2009 12:57 AM, Randy Dunlap wrote:
> From: Randy Dunlap <randy.dunlap@oracle.com>
>
> Fix printk format warnings in osd_uld:
>
> drivers/scsi/osd/osd_uld.c:191: warning:format '%s' expects type 'char *', but argument 2 has type 'struct path'
>
> Also fix a small typo.
>
> Signed-off-by: Randy Dunlap <randy.dunlap@oracle.com>
> ---
> drivers/scsi/osd/osd_uld.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> --- linux-next-20090423.orig/drivers/scsi/osd/osd_uld.c
> +++ linux-next-20090423/drivers/scsi/osd/osd_uld.c
> @@ -188,7 +188,7 @@ struct osd_dev *osduld_path_lookup(const
>
> error = kern_path(name, LOOKUP_FOLLOW, &path);
> if (error) {
> - OSD_ERR("path_lookup of %s faild=>%d\n", path, error);
> + OSD_ERR("path_lookup of %s failed=>%d\n", name, error);
> return ERR_PTR(error);
> }
>
>
Hi Randy thanks for the catch.
I cannot do anything with this patch as it is a fallout of an
Al Viro's patch which I do not have access to, from any of my trees.
This is:
Reduce path_lookup() abuses
use kern_path() where possible
Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
(Linux-next's fe48fce1a72439d1b70dc8a9bce80c46ac4a6c96)
Al hi
Thanks for the fix and simplification. At the time of writing this I
did not find the kern_path(), which is much better in this code, Sorry.
Please squash or apply above Randy's patch. And tell me where I can find
it so I can test it and send an ACK-BY if that's needed. (Or if you want
that I pick this code, I'm here to help)
Thanks a lot for fixing this code
Boaz
next prev parent reply other threads:[~2009-04-26 15:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-23 21:57 [PATCH -next] osd_uld: fix printk format warning Randy Dunlap
2009-04-26 15:32 ` Boaz Harrosh [this message]
[not found] <20090429092631.a76e79c5.randy.dunlap@oracle.com>
2009-04-29 18:51 ` 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
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=49F47EA9.3070204@panasas.com \
--to=bharrosh@panasas.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=linux-scsi@vger.kernel.org \
--cc=randy.dunlap@oracle.com \
--cc=viro@zeniv.linux.org.uk \
/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