[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <9a8748490708301604k688daad8p145fb9106b442d91@mail.gmail.com>
Date: Fri, 31 Aug 2007 01:04:09 +0200
From: "Jesper Juhl" <jesper.juhl@...il.com>
To: "Randy Dunlap" <randy.dunlap@...cle.com>
Cc: "Joe Perches" <joe@...ches.com>, "Daniel Drake" <dsd@...too.org>,
"Linux Kernel Mailing List" <linux-kernel@...r.kernel.org>,
netdev@...r.kernel.org, "David S. Miller" <davem@...emloft.net>,
"Ulrich Kunitz" <kune@...ne-taler.de>,
linux-wireless@...r.kernel.org
Subject: Re: [PATCH] Don't needlessly initialize variable to NULL in zd_chip (was: Re: [PATCH 13/30] net: Don't do pointless kmalloc return value casts in zd1211 driver)
On 31/08/2007, Randy Dunlap <randy.dunlap@...cle.com> wrote:
...
>
> BTW: http://marc.info/?l=linux-wireless&m=118831813500769&w=2
>
...
Heh, thanks Randy.
All too often patches get missed since I don't happen to include the
right magic person to Cc. So I generally take a "better to have one Cc
too many than miss one" approach when sending patches - otherwise I
just end up resending it several times and eventually have to bother
Andrew to move it through -mm.
I see the point of people not getting things twice, but too many
patches slip through the cracks already (and not just my patches,
that's a general problem) so I'd rather inconvenience a few people
with one extra email than missing the proper maintainer by not Cc'ing
the right list. Picking the right list/set of people to Cc is hard!
(whoops, mistakenly didn't do a reply-to-all initially; sorry Randy,
now you'll get this mail twice ;)
--
Jesper Juhl <jesper.juhl@...il.com>
Don't top-post http://www.catb.org/~esr/jargon/html/T/top-post.html
Plain text mails only, please http://www.expita.com/nomime.html
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists