From: Stephen Hemminger <shemminger@osdl.org>
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: davem@davemloft.net, netdev <netdev@vger.kernel.org>
Subject: Re: [PATCH] bridge: correct print message typo
Date: Tue, 24 Oct 2006 22:49:09 -0700 [thread overview]
Message-ID: <453EFAD5.60707@osdl.org> (raw)
In-Reply-To: <20061024212458.58a36232.randy.dunlap@oracle.com>
Randy Dunlap wrote:
> From: Randy Dunlap <randy.dunlap@oracle.com>
>
> Correct message typo/spello.
>
> Signed-off-by: Randy Dunlap <randy.dunlap@oracle.com>
> ---
> net/bridge/br_sysfs_br.c | 2 +-
> 1 files changed, 1 insertion(+), 1 deletion(-)
>
> --- linux-2619-rc3-pv.orig/net/bridge/br_sysfs_br.c
> +++ linux-2619-rc3-pv/net/bridge/br_sysfs_br.c
> @@ -376,7 +376,7 @@ int br_sysfs_addbr(struct net_device *de
>
> err = sysfs_create_bin_file(brobj, &bridge_forward);
> if (err) {
> - pr_info("%s: can't create attribue file %s/%s\n",
> + pr_info("%s: can't create attribute file %s/%s\n",
> __FUNCTION__, dev->name, bridge_forward.attr.name);
> goto out2;
> }
>
>
> ---
>
no problemo.
next prev parent reply other threads:[~2006-10-25 5:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-25 4:24 [PATCH] bridge: correct print message typo Randy Dunlap
2006-10-25 5:49 ` Stephen Hemminger [this message]
2006-10-26 6:07 ` David Miller
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=453EFAD5.60707@osdl.org \
--to=shemminger@osdl.org \
--cc=davem@davemloft.net \
--cc=netdev@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 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).