From: Joe Perches <joe@perches.com>
To: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
Cc: Simon Horman <horms@verge.net.au>,
netdev@vger.kernel.org, linux-sh@vger.kernel.org
Subject: Re: [PATCH] sh_eth: fix garbled TX error message
Date: Mon, 13 Jan 2014 08:51:58 -0800 [thread overview]
Message-ID: <1389631918.24849.20.camel@joe-AO722> (raw)
In-Reply-To: <52D41117.3040809@cogentembedded.com>
On Mon, 2014-01-13 at 20:15 +0400, Sergei Shtylyov wrote:
> On 13-012014 5:24, Joe Perches wrote:
> >>> sh_eth_error() in case of a TX error tries to print a message using 2 dev_err()
> >>> calls with the first string not finished by '\n', so that the resulting message
> >>> would inevitably come out garbled, with something like "3net eth0: " inserted
> >>> in the middle. Avoid that by merging 2 calls into one.
>
> > I believe this interleaving should not happen since
> > commit e28d713704117bca0820c732210df6075b09f13b
> > (2.6.31 days)
>
> I believe you have given me the wrong commit, which has nothing to do the
> the newline problem per se. It just adds KERN_DEFAULT. I was able to find the
> correct commit though: it's the parent of the commit you cited,
Yeah, I was just scanning the printk commit logs
and looked for the first one that said something
like force newline.
> I should have tested my assumption beforehand...
Always a good thing.
> (I'd like to merge these
> dev_err() calls still though).
Yes, the dev_err calls should be merged.
About the other stuff, what/when ever...
cheers, Joe
next prev parent reply other threads:[~2014-01-13 16:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-10 23:41 [PATCH] sh_eth: fix garbled TX error message Sergei Shtylyov
2014-01-13 0:45 ` Simon Horman
2014-01-13 1:24 ` Joe Perches
2014-01-13 16:15 ` Sergei Shtylyov
2014-01-13 16:51 ` Joe Perches [this message]
2014-01-14 7:29 ` David Miller
2014-01-14 11:49 ` Sergei Shtylyov
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=1389631918.24849.20.camel@joe-AO722 \
--to=joe@perches.com \
--cc=horms@verge.net.au \
--cc=linux-sh@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=sergei.shtylyov@cogentembedded.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