From: Kalle Valo <kalle.valo@nokia.com>
To: Roel Kluin <12o3l@tiscali.nl>
Cc: David Miller <davem@davemloft.net>, netdev@vger.kernel.org
Subject: Re: drivers/net/niu.c: memcpy(dev->dev_addr, dev->perm_addr, dev->addr_len)?
Date: Fri, 21 Mar 2008 15:07:27 +0200 [thread overview]
Message-ID: <87iqzgql80.fsf@nokia.com> (raw)
In-Reply-To: <47E2ECB7.5030304@tiscali.nl> (ext Roel Kluin's message of "Fri\, 21 Mar 2008 00\:01\:11 +0100")
Roel Kluin <12o3l@tiscali.nl> writes:
>> I notice you posting several of these kinds of things.
>
> Only 2 with the above conditions and patches or not where I was able to
> figure it out myself. I don't really understand why you are opposed to
> these questions.
Because it will take developer's time from fixing real bugs. Time is
scarce and email takes way too much of people's time already. You will
understand this when you start getting too many emails.
--
Kalle Valo
next prev parent reply other threads:[~2008-03-21 13:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-20 21:01 drivers/net/niu.c: memcpy(dev->dev_addr, dev->perm_addr, dev->addr_len)? Roel Kluin
2008-03-20 21:25 ` David Miller
2008-03-20 23:01 ` Roel Kluin
2008-03-21 13:07 ` Kalle Valo [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-03-20 21:01 Roel Kluin
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=87iqzgql80.fsf@nokia.com \
--to=kalle.valo@nokia.com \
--cc=12o3l@tiscali.nl \
--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).