From: Andrew Morton <akpm@linux-foundation.org>
To: Timo Witte <timo.witte@googlemail.com>
Cc: linux-kernel@vger.kernel.org, Steve French <sfrench@samba.org>
Subject: Re: [PATCH] /fs/cifs HEAD
Date: Thu, 1 Apr 2010 11:56:20 -0700 [thread overview]
Message-ID: <20100401115620.41821f7d.akpm@linux-foundation.org> (raw)
In-Reply-To: <a3177ec71003290139w3f435bddv25e06a576afabb07@mail.gmail.com>
On Mon, 29 Mar 2010 10:39:12 +0200
Timo Witte <timo.witte@googlemail.com> wrote:
> commit 4baf102b1db4ba5c91532acf84acdb9c31867fe6
> Author: Timo Witte <timo.witte@googlemail.com>
> Date: __ Mon Mar 29 10:20:09 2010 +0200
> ____ __added additional info to error message in cifs
> diff --git a/fs/cifs/dns_resolve.c b/fs/cifs/dns_resolve.c
> index 8794814..28b588c 100644
> --- a/fs/cifs/dns_resolve.c
> +++ b/fs/cifs/dns_resolve.c
> @@ -137,7 +137,7 @@ dns_resolve_server_name_to_ip(const char *unc,
> char **ip_addr)
> len = rkey->type_data.x[0];
> data = rkey->payload.data;
> } else {
> - cERROR(1, ("%s: unable to resolve: %s", func, name));
> + cERROR(1, ("%s: unable to resolve: %s have you
> installed /sbin/request-key ?", func, name));
> goto out;
> }
OK, I can see how that would save someone a lot of time.
Your patch did basically everything wrong: meaningless title,
wordwrapped, changelog doesn't explain the reason for making the patch,
missing Signed-off-by:, didn't cc: the maintainer, gmail-inserted
non-ascii chanracters, tabs replaced by spaces (gmail again).
I typed it in again ;)
Subject: cifs: provide user with a hint when name resolution fails
From: Timo Witte <timo.witte@googlemail.com>
Cc: Steve French <sfrench@samba.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
fs/cifs/dns_resolve.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff -puN fs/cifs/dns_resolve.c~cifs-provide-user-with-a-hint-when-name-resolution-fails fs/cifs/dns_resolve.c
--- a/fs/cifs/dns_resolve.c~cifs-provide-user-with-a-hint-when-name-resolution-fails
+++ a/fs/cifs/dns_resolve.c
@@ -138,7 +138,8 @@ dns_resolve_server_name_to_ip(const char
len = rkey->type_data.x[0];
data = rkey->payload.data;
} else {
- cERROR(1, ("%s: unable to resolve: %s", __func__, name));
+ cERROR(1, ("%s: unable to resolve: %s have you "
+ "installed /sbin/request-key ?", __func__, name));
goto out;
}
_
next prev parent reply other threads:[~2010-04-01 18:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-29 8:39 Timo Witte
2010-04-01 18:56 ` Andrew Morton [this message]
2010-04-01 19:18 ` Joe Perches
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=20100401115620.41821f7d.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sfrench@samba.org \
--cc=timo.witte@googlemail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome