From: Timur Tabi <timur@freescale.com>
To: David Miller <davem@davemloft.net>
Cc: <david.daney@cavium.com>, <netdev@vger.kernel.org>
Subject: Re: [PATCH] netdev/phy: skip disabled mdio-mux nodes
Date: Tue, 14 Aug 2012 16:12:10 -0500 [thread overview]
Message-ID: <502ABF2A.9070605@freescale.com> (raw)
In-Reply-To: <20120814.140736.812697309119422215.davem@davemloft.net>
David Miller wrote:
>> Any chance this patch can get into 3.6? I don't know if it qualifies
>> as a fix or not, but getting it into 3.6 would make it easier for me
>> to apply other patches to the powerpc tree.
>>
>
> I want you to implement it the way David Daney said to do so.
So you're saying that you don't want this fixed for 3.6? Because David
Daney's suggestion would require me to introduce a new device tree
function, and that won't be accepted until 3.7 at the earliest.
> And you never need to ask me questions like this, I clearly mark the
> state of your patch:
>
> http://patchwork.ozlabs.org/patch/175750/
>
> So that you can just monitor it instead of wasting my time asking what
> is happening to your patch.
Sorry.
> Time of mine you consume forcing me to reply to you in situations like
> this, which you could handle on your own, is time that I can't spend
> reviewing patches from oher people that really are ready to go into
> the tree.
>
--
Timur Tabi
Linux kernel developer at Freescale
next prev parent reply other threads:[~2012-08-14 21:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-07 16:51 [PATCH] netdev/phy: skip disabled mdio-mux nodes Timur Tabi
2012-08-07 16:59 ` David Daney
[not found] ` <5021496D.8070200-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2012-08-07 17:04 ` Timur Tabi
2012-08-14 19:19 ` Tabi Timur-B04825
2012-08-14 21:07 ` David Miller
2012-08-14 21:12 ` Timur Tabi [this message]
2012-08-14 21:16 ` David Miller
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=502ABF2A.9070605@freescale.com \
--to=timur@freescale.com \
--cc=davem@davemloft.net \
--cc=david.daney@cavium.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.