From: David Miller <davem@davemloft.net>
To: mpatocka@redhat.com
Cc: stephen@networkplumber.org, sparclinux@vger.kernel.org,
netdev@vger.kernel.org
Subject: Re: [PATCH] sunhme: convert printk to pr_cont
Date: Fri, 17 Aug 2018 13:21:44 -0700 (PDT) [thread overview]
Message-ID: <20180817.132144.829402142627411604.davem@davemloft.net> (raw)
In-Reply-To: <alpine.LRH.2.02.1808171606520.2385@file01.intranet.prod.int.rdu2.redhat.com>
From: Mikulas Patocka <mpatocka@redhat.com>
Date: Fri, 17 Aug 2018 16:08:49 -0400 (EDT)
> I'm not an expert on networking code - you can change it if it is more
> appropriate this way.
What Stephen is asking of you doesn't require networking expertiece
and he even gave you an example of how to do it. All you would need
to do is test is suggestion and make sure it works properly.
prev parent reply other threads:[~2018-08-17 23:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-17 19:12 [PATCH] sunhme: convert printk to pr_cont Mikulas Patocka
2018-08-17 19:27 ` David Miller
2018-08-17 19:52 ` Stephen Hemminger
2018-08-17 20:08 ` Mikulas Patocka
2018-08-17 20:21 ` David Miller [this message]
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=20180817.132144.829402142627411604.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=mpatocka@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=sparclinux@vger.kernel.org \
--cc=stephen@networkplumber.org \
/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).