netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: shemminger@vyatta.com
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH 0/8] sky2: driver update
Date: Sun, 09 Aug 2009 21:09:43 -0700 (PDT)	[thread overview]
Message-ID: <20090809.210943.256633746.davem@davemloft.net> (raw)
In-Reply-To: <20090806161213.148382653@vyatta.com>

From: Stephen Hemminger <shemminger@vyatta.com>
Date: Thu, 06 Aug 2009 09:12:13 -0700

> This undoes the prematurely committed sky2 transmit logic changes
> and applies Mike's later changes.
> Here is a corrected patch stream please apply this to 2.6.31-rc5

I have to pass on this set, too many problems:

1) You didn't provide explicit "From: " lines for patches where
   you were not the author Stephen.  I could guess from the
   Signoff lines but I'd rather not.

2) I can almost swallow the cleanups if they make the bug fix
   coming up afterwards to be understood more easily.

   But I'm not going to apply patches right now that remove locking
   beause it "seems safe" or "should be ok".  That's absolutely not
   appropriate right now unless it fixes a performance regression
   explicitly listed in the formal regression list.  This is in
   reference to patch #5.

   If this is a prerequisite for patch #6 in some way (that's my
   guess), please make this more explicit, or even better change
   words like "should" (that sounds like "I'm not sure") into
   "is" when the commit message describes how the locks are no
   longer needed at that spot.

   Another idea is to combine #5 and #6 and explain the dependency
   in the commit message.

Also, to be honest, this kind of commit count is way too high at this
late stage of the RC series.  Nothing in here is super critical,
and none of it (to my knowledge) is in the regression list either.

And I informed you in private that the main reason I kept asking you
to be more responsive over the past month or so to sky2 patches and
bug reports was so that patches trickled in gradually, instead of
being dumped all at once way too late in the RC series.

  parent reply	other threads:[~2009-08-10  4:09 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-06 16:12 [PATCH 0/8] sky2: driver update Stephen Hemminger
2009-08-06 16:12 ` [PATCH 1/8] Revert "sky2: Avoid transmits during sky2_down()" Stephen Hemminger
2009-08-06 16:12 ` [PATCH 2/8] sky2: Avoid rewinding sky2->tx_prod Stephen Hemminger
2009-08-06 16:12 ` [PATCH 3/8] sky2: Move tx reset functionality to sky2_tx_reset() Stephen Hemminger
2009-08-06 16:12 ` [PATCH 4/8] sky2: Reset tx train after interrupts disabled Stephen Hemminger
2009-08-06 16:12 ` [PATCH 5/8] sky2: Remove tx locks Stephen Hemminger
2009-08-06 16:12 ` [PATCH 6/8] sky2: Lock tx queue when calling sky2_down locally Stephen Hemminger
2009-08-06 16:12 ` [PATCH 7/8] sky2: hold RTNL when doing suspend/shutdown operations Stephen Hemminger
2009-08-06 16:12 ` [PATCH 8/8] sky2: hold spinlock around phy_power_down Stephen Hemminger
2009-08-10  4:09 ` David Miller [this message]
2009-08-10 15:48   ` [PATCH 0/8] sky2: driver update Stephen Hemminger
2009-08-11  0: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=20090809.210943.256633746.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=netdev@vger.kernel.org \
    --cc=shemminger@vyatta.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;
as well as URLs for NNTP newsgroup(s).