public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg Ungerer <gerg@snapgear.com>
To: David Miller <davem@davemloft.net>
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: Tue, 07 Jul 2009 11:37:18 +1000	[thread overview]
Message-ID: <4A52A6CE.6010509@snapgear.com> (raw)
In-Reply-To: <20090706.182704.192109619.davem@davemloft.net>

Hi David,

David Miller wrote:
> 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

That is not a cleanup patch. It is a bug fix. You cannot build
with those ";" in there:

   CC      drivers/net/fec.o
In file included from drivers/net/fec.c:51:
drivers/net/fec.h:49:19: warning: missing whitespace after the macro name
drivers/net/fec.h:50:19: warning: missing whitespace after the macro name
drivers/net/fec.h:51:18: warning: missing whitespace after the macro name
drivers/net/fec.h:52:17: warning: missing whitespace after the macro name
drivers/net/fec.h:53:25: warning: missing whitespace after the macro name
drivers/net/fec.h:54:25: warning: missing whitespace after the macro name
drivers/net/fec.c: In function ‘fec_enet_start_xmit’:
drivers/net/fec.c:352: error: expected expression before ‘;’ token
drivers/net/fec.c: In function ‘fec_enet_interrupt’:


> 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.

Care to reconsider?

Regards
Greg


------------------------------------------------------------------------
Greg Ungerer  --  Principal Engineer        EMAIL:     gerg@snapgear.com
SnapGear Group, McAfee                      PHONE:       +61 7 3435 2888
825 Stanley St,                             FAX:         +61 7 3891 3630
Woolloongabba, QLD, 4102, Australia         WEB: http://www.SnapGear.com

  reply	other threads:[~2009-07-07  1:37 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
2009-07-07  1:37   ` Greg Ungerer [this message]
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=4A52A6CE.6010509@snapgear.com \
    --to=gerg@snapgear.com \
    --cc=davem@davemloft.net \
    --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