From: Varka Bhadram <varkabhadram@gmail.com>
To: David Miller <davem@davemloft.net>, varkabhadram@gmail.com
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH net-next v2 1/2] ethernet: realtek: use module_pci_driver
Date: Tue, 22 Jul 2014 13:54:17 +0530 [thread overview]
Message-ID: <53CE1FB1.6020809@gmail.com> (raw)
In-Reply-To: <20140722.002850.1113335731441581168.davem@davemloft.net>
On 07/22/2014 12:58 PM, David Miller wrote:
> From: varkabhadram@gmail.com
> Date: Tue, 22 Jul 2014 12:50:21 +0530
>
>> @@ -1887,11 +1887,7 @@ static int cp_init_one (struct pci_dev *pdev, const struct pci_device_id *ent)
>> resource_size_t pciaddr;
>> unsigned int addr_len, i, pci_using_dac;
>>
>> -#ifndef MODULE
>> - static int version_printed;
>> - if (version_printed++ == 0)
>> - pr_info("%s", version);
>> -#endif
>> + pr_info("%s", version);
> Now you're changing behavior undesirably, it will now print the
> version string into the logs for every instance of the device which is
> discovered.
>
> Seriously, the driver is worse off after these "cleanups".
Here we are having two possibilities here:
1. Removing the version info completely. Ofcourse this is not desirable.
2. Accepting the version info to be print into log messages.
I will put like this by removing #ifdefs:
static int version_printed;
if (version_printed++ == 0)
pr_info("%s", version);
Will it be OK ..?
--
Regards,
Varka Bhadram.
next prev parent reply other threads:[~2014-07-22 8:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-22 7:20 [PATCH net-next v2 0/2] cleanup for Realtek 8139CP varkabhadram
2014-07-22 7:20 ` [PATCH net-next v2 1/2] ethernet: realtek: use module_pci_driver varkabhadram
2014-07-22 7:28 ` David Miller
2014-07-22 8:24 ` Varka Bhadram [this message]
2014-07-22 14:38 ` Sergei Shtylyov
2014-07-22 14:43 ` Varka Bhadram
2014-07-22 15:01 ` Sergei Shtylyov
2014-07-22 15:03 ` Varka Bhadram
2014-07-22 7:20 ` [PATCH net-next v2 2/2] ethernet: realtek: use pci_device_id varkabhadram
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=53CE1FB1.6020809@gmail.com \
--to=varkabhadram@gmail.com \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.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).