netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Pradeep A. Dalvi" <netdev@pradeepdalvi.com>
To: David Miller <davem@davemloft.net>
Cc: eric.dumazet@gmail.com, netdev@vger.kernel.org, hch@lst.de,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/1] netdev/ethernet: dev_alloc_skb to netdev_alloc_skb
Date: Sun, 22 Jan 2012 00:47:47 +0530	[thread overview]
Message-ID: <CA+Dx6Hbbe0OadeyNQtO1__dU3K5VSecHajFQPSJiD=GSci+Nqw@mail.gmail.com> (raw)
In-Reply-To: <20120121.133933.227768598621914035.davem@davemloft.net>

On Sun, Jan 22, 2012 at 12:09 AM, David Miller <davem@davemloft.net> wrote:
> From: "Pradeep A. Dalvi" <netdev@pradeepdalvi.com>
> Date: Sat, 21 Jan 2012 22:16:06 +0530
>
>> I appreciate your concerns. Although I feel, it is essential to add
>> relevant comments by respective (corporate/paid :-) developers, if
>> their hardware needs hardcoded 2. And especially, if their expectation
>> is to buy their hardware, even for the smaller purpose of having
>> uniform mechanism. Long live Open Source! :-)
>
> I see the smiley but it is your responsibility to learn how a driver
> works before making changes to it that break them.  Stop talking such
> foolishness, it is very unbecoming of a serious developer.

Certainly! I completely agree to the point of being responsible
contributor and in another words, not to break existing things due to
lack of information.
Although I mentioned so, due to realized importance of
comments/documentation over the expectations of owning hardware for
testing. Especially, if those points are so much critical to the
hardware. And also more importantly, while accessing Kernel resources.
Anyways, I would avoid touching +2 further, like I've avoided for +3,
+4, +5 and so on, in this patch & resubmit the patch. Thanks!

      reply	other threads:[~2012-01-21 19:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-21 14:43 [PATCH 1/1] netdev/ethernet: dev_alloc_skb to netdev_alloc_skb Pradeep A. Dalvi
2012-01-21 15:53 ` Eric Dumazet
2012-01-21 16:46   ` Pradeep A. Dalvi
2012-01-21 18:39     ` David Miller
2012-01-21 19:17       ` Pradeep A. Dalvi [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='CA+Dx6Hbbe0OadeyNQtO1__dU3K5VSecHajFQPSJiD=GSci+Nqw@mail.gmail.com' \
    --to=netdev@pradeepdalvi.com \
    --cc=davem@davemloft.net \
    --cc=eric.dumazet@gmail.com \
    --cc=hch@lst.de \
    --cc=linux-kernel@vger.kernel.org \
    --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).