linux-kernel - Re: [PATCH] I2C: add support for the PCF8575 chip

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20071023135030.750e9fa4@hyperion.delvare>
Date:	Tue, 23 Oct 2007 13:50:30 +0200
From:	Jean Delvare <khali@...ux-fr.org>
To:	Andrew Morton <akpm@...ux-foundation.org>
Cc:	"Bart Van Assche" <bart.vanassche@...il.com>,
	linux-kernel@...r.kernel.org, i2c@...sensors.org
Subject: Re: [PATCH] I2C: add support for the PCF8575 chip

Hi Andrew,

On Mon, 22 Oct 2007 14:58:14 -0700, Andrew Morton wrote:
> On Fri, 5 Oct 2007 11:32:35 +0200
> "Bart Van Assche" <bart.vanassche@...il.com> wrote:
> 
> > From: Bart Van Assche
> > 
> > Add support for the PCF8575 I2C chip.
> 
> I'll comment on this 17-day-old patch.
> 
> Jean, this illustrates why explicitly steering people *away* from lkml or
> from any other mailing list is a poor idea.  If Bart has posted an updated
> version to the i2c list then I end up reviewing an outdated patch, and
> probably duplicating other people's comments.

You're unfair. I can use the same argument the other way around: if
Bart did not post to the wrong list in the first place, then there
would have been no risk for you to miss any update.

I stand on my initial affirmation that sending all patches, bug reports
etc. to LKML when more specialized lists exist, is a bad idea. Maybe it
makes you happy because you want to know everything that's going on in
every area on the kernel, and are lucky enough to be able to actually
do that and survive. But for others, it's essentially wasting their
time (not to mention bandwidth and disk space.)

If you are so interested about i2c patches, then I'd suggest that you
simply subscribe to the i2c list.

> googling for 'PCF8575 Assche' indicates that he has not sent an updated
> patch.  Perhaps he was discouraged by your quite unconstructive response.

Actually Bart resent his patch to the i2c list 3 days later, twice. But
it was probably the exact same patch (it didn't mention any changes at
least.) There's no reason why Bart would have sent an updated patch as
he did not receive feedback at this point. I fail to see how my
response would have had any influence in that respect.

Anyway, thanks for the review. I didn't have much time left for reviews
these last few weeks.

Still... I am worried that you, Andrew Morton, co-top-maintainer of the
Linux 2.6 kernel, one of most brilliant kernel developers we have,
waste your time doing the initial review of a random i2c patch that
about anyone remotely involved in kernel development would have been
able to review. There's something wrong here.

-- 
Jean Delvare
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/