From: Lee Jones <lee.jones@linaro.org>
To: Laszlo Papp <lpapp@kde.org>
Cc: Jean Delvare <jdelvare@suse.de>,
LKML <linux-kernel@vger.kernel.org>,
lm-sensors@lm-sensors.org, Guenter Roeck <linux@roeck-us.net>
Subject: Re: [lm-sensors] [RFC PATCH] hwmon: (max6650) Convert to be a platform driver
Date: Thu, 13 Feb 2014 11:33:13 +0000 [thread overview]
Message-ID: <20140213113313.GL32508@lee--X1> (raw)
In-Reply-To: <CAOMwXhOv-as1W69wcSno49jEXsXWZZ7odnu8og-vgnDwRTJ4sA@mail.gmail.com>
> >>> > -static int max6650_probe(struct i2c_client *client,
> >>> > - const struct i2c_device_id *id);
> >>> > -static int max6650_init_client(struct i2c_client *client);
> >>> > -static int max6650_remove(struct i2c_client *client);
> >>> > +static int max6650_probe(struct platform_device *pdev);
> >>> > +static int max6650_init_client(struct platform_device *pdev);
> >>> > +static int max6650_remove(struct platform_device *pdev);
> >>> > static struct max6650_data *max6650_update_device(struct device *dev);
> >>>
> >>> It would be good to remove these forward declarations in the future.
> >>>
> >>> If no one volunteers I'll happily do it.
> >>
> >> Guenter just did:
> >>
> >> http://lists.lm-sensors.org/pipermail/lm-sensors/2014-February/041224.html
> >>
> >> Any change to the max6650 driver should go on top of his patch series
> >> to avoid conflicts:
> >>
> >> http://lists.lm-sensors.org/pipermail/lm-sensors/2014-February/041223.html
> >
> As far as I can see, that patch set was not even tested, so how can it
> go in? I was told that any patch should be _runtime_ tested, too.
> Fwiw, I do not have time to test those personally, he would need to
> find someone else if that requirement really holds true.
>
> I would not really like to fix bugs appearing in that code to get my
> features in.
>
> Also, since my change has been around for 2-3 months now, I would
> really prefer not to be forced to rewrite it again from scratch.
> Surely, you can wait with those, more or less, cosmetic non-runtime
> tested changes?
>
> This would impose me a lot of additional work again, and I personally
> do not see the benefit of it. In my book at least, feature is over
> internal polishing.
Right, I've had enough. I'm removing your patch from the MFD tree.
I've asked too many people to give you a second chance and asked you
privately to behave yourself and treat others with respect. So far I
haven't seen an ounce of self control or depomacy from you.
This is how it's going to work from now on:
- You submit a patch
- It gets reviewed <----\
- You fix up the review comments as requested -----/
- Non-compliance or arguments with the _experts_ results in:
`$INTEREST > /dev/null || \
grep "From: Laszio Papp" ~/.mail | xargs rm -rf`
--
Lee Jones
Linaro STMicroelectronics Landing Team Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
next prev parent reply other threads:[~2014-02-13 11:33 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-13 8:50 [RFC PATCH] hwmon: (max6650) Convert to be a platform driver Laszlo Papp
2014-02-13 9:58 ` Lee Jones
2014-02-13 10:15 ` [lm-sensors] " Jean Delvare
2014-02-13 10:38 ` Laszlo Papp
2014-02-13 10:46 ` Laszlo Papp
2014-02-13 11:07 ` Jean Delvare
2014-02-13 11:29 ` Laszlo Papp
2014-02-13 11:33 ` Lee Jones [this message]
2014-02-13 12:27 ` Laszlo Papp
2014-02-13 12:40 ` Lee Jones
2014-02-14 7:03 ` Laszlo Papp
2014-02-14 9:02 ` Lee Jones
2014-02-14 9:20 ` Laszlo Papp
2014-02-14 10:17 ` Lee Jones
2014-02-13 12:57 ` Jean Delvare
2014-02-13 13:19 ` Laszlo Papp
2014-02-13 16:16 ` Guenter Roeck
2014-02-13 16:53 ` Laszlo Papp
2014-02-14 9:13 ` Lee Jones
2014-02-13 11:16 ` Lee Jones
2014-02-13 11:58 ` Jean Delvare
2014-02-13 16:29 ` Guenter Roeck
2014-02-13 10:55 ` Laszlo Papp
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=20140213113313.GL32508@lee--X1 \
--to=lee.jones@linaro.org \
--cc=jdelvare@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=lm-sensors@lm-sensors.org \
--cc=lpapp@kde.org \
/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