public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: gerg@snapgear.com
Cc: netdev@vger.kernel.org, gerg@uclinux.org, s.hauer@pengutronix.de
Subject: Re: [PATCH] fec: fix definition of 5272 version of FEC_X_DES_ACTIVE register
Date: Mon, 06 Jul 2009 18:27:04 -0700 (PDT)	[thread overview]
Message-ID: <20090706.182704.192109619.davem@davemloft.net> (raw)
In-Reply-To: <200907070123.n671NY36005818@localhost.localdomain>

From: Greg Ungerer <gerg@snapgear.com>
Date: Tue, 7 Jul 2009 11:23:34 +1000

> fec: fix definition of 5272 version of FEC_X_DES_ACTIVE register
> 
> The ColdFire 5272 FEC driver has a different register address map
> than other users of the FEC driver. And its definition of the
> FEC_X_DES_ACTIVE register is incorrect, it should be 0x14.
> The fec interface cannot transmit data with the old value.
> 
> Signed-off-by: Greg Ungerer <gerg@uclinux.org>

This wasn't handled well at all.

You sent me what amounted to a cleanup patch to remove the
trailing ";" in these definitions first.  I can only put
that into net-next-2.6

Now you send me a real bug fix for one of these macro
values and it only applies on top of that ";" removal
patch.

That completely sucks.  Now I can't just apply this to
net-2.6 to get the bug fixed.

You should have sent just the bug fix, then waited a week
or so for the net-2.6 tree to get merged into the net-next-2.6
tree and then you could send the ";" cleanup cleanly on top
of that.

I can't apply this so I'm rejecting it in patchwork.

  reply	other threads:[~2009-07-07  1:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-07  1:23 [PATCH] fec: fix definition of 5272 version of FEC_X_DES_ACTIVE register Greg Ungerer
2009-07-07  1:27 ` David Miller [this message]
2009-07-07  1:37   ` Greg Ungerer
2009-07-07  1:52     ` 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=20090706.182704.192109619.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=gerg@snapgear.com \
    --cc=gerg@uclinux.org \
    --cc=netdev@vger.kernel.org \
    --cc=s.hauer@pengutronix.de \
    /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