public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: sfking@fdwdc.com
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH] fec: fix clk handling for Coldfire.
Date: Sun, 17 Jun 2012 02:00:01 -0700 (PDT)	[thread overview]
Message-ID: <20120617.020001.1114007088096967861.davem@davemloft.net> (raw)
In-Reply-To: <201206170121.18807.sfking@fdwdc.com>

From: Steven King <sfking@fdwdc.com>
Date: Sun, 17 Jun 2012 01:21:18 -0700

> On Sunday 17 June 2012 1:08:49 am David Miller wrote:
>> Sorry, I'm not going to allow you to crap up this driver with
>> ifdefs.  Find a way to fix it without that.
> 
> Well, then how about then revert the commit and have the imx folks
> do whatever they need to do without breaking things for Coldfire?

Read what I said, you have the time to fix the problem cleanly.
It's not like there's a kernel release tomorrow.

      reply	other threads:[~2012-06-17  9:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-17  7:00 [PATCH] fec: fix clk handling for Coldfire Steven King
2012-06-17  8:08 ` David Miller
2012-06-17  8:21   ` Steven King
2012-06-17  9:00     ` 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=20120617.020001.1114007088096967861.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=netdev@vger.kernel.org \
    --cc=sfking@fdwdc.com \
    /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