From: Javier Martinez Canillas <javier@dowhile0.org> To: "Pali Rohár" <pali.rohar@gmail.com> Cc: Pavel Machek <pavel@ucw.cz>, Sebastian Reichel <sre@kernel.org>, Sakari Ailus <sakari.ailus@iki.fi>, Andrew Morton <akpm@osdl.org>, kernel list <linux-kernel@vger.kernel.org>, linux-arm-kernel <linux-arm-kernel@lists.infradead.org>, "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>, Tony Lindgren <tony@atomide.com>, Kevin Hilman <khilman@kernel.org>, Aaro Koskinen <aaro.koskinen@iki.fi>, ivo.g.dimitrov.75@gmail.com, Patrik Bachan <patrikbachan@gmail.com>, Kumar Gala <galak@codeaurora.org>, Benoit Cousson <bcousson@baylibre.com>, m.chehab@samsung.com, "devicetree@vger.kernel.org" <devicetree@vger.kernel.org>, mchehab@osg.samsung.com, hverkuil@xs4all.nl Subject: Re: [PATCHv7] media: i2c/adp1653: fix includes Date: Mon, 13 Apr 2015 10:32:16 +0200 [thread overview] Message-ID: <CABxcv==j=GLq0o6Shr32-81-6o0z4mSMOm7c_4Q1e+rQBgdEKQ@mail.gmail.com> (raw) In-Reply-To: <20150409125927.GC12339@atrey.karlin.mff.cuni.cz> Hello Pali, On Thu, Apr 9, 2015 at 2:59 PM, Pali Rohár <pali.rohar@gmail.com> wrote: > On Thursday 09 April 2015 14:43:59 Javier Martinez Canillas wrote: >> >> Please re-spin your previous patch and submit it properly. >> >> Best regards, >> Javier > > Hi all! What about stopping this meaningless discussion about resending > full patch series when everybody know how to fix is quickly in editor > (e.g with sed under 5s) and not wasting another 10 minutes to generate > new unified diff sent via SMTP protocol? > No, there is a reason why we have written rules on how patches should be submitted. Everyone in the kernel community is expected to optimize their workflow according to these rules to make life easier for people reviewing and merging the patches. As you said now someone has to fix this using an editor and that is an error prone process. Besides, why it would take 10 minutes to generate a proper patch-set? git is very good on this regard (i.e: git commit ---fixup && git rebase -i && git format-patch && git send-email). I won't argue anymore but I find very sad that people who have been in the kernel community for years don't follow the basic rules we have documented it. So I wonder why we have the documentation in the first place and how can we expect newcomers to follow if even experienced kernel hackers don't. > -- > Pali Rohár > pali.rohar@gmail.com Best regards, Javier
WARNING: multiple messages have this Message-ID (diff)
From: javier@dowhile0.org (Javier Martinez Canillas) To: linux-arm-kernel@lists.infradead.org Subject: [PATCHv7] media: i2c/adp1653: fix includes Date: Mon, 13 Apr 2015 10:32:16 +0200 [thread overview] Message-ID: <CABxcv==j=GLq0o6Shr32-81-6o0z4mSMOm7c_4Q1e+rQBgdEKQ@mail.gmail.com> (raw) In-Reply-To: <20150409125927.GC12339@atrey.karlin.mff.cuni.cz> Hello Pali, On Thu, Apr 9, 2015 at 2:59 PM, Pali Roh?r <pali.rohar@gmail.com> wrote: > On Thursday 09 April 2015 14:43:59 Javier Martinez Canillas wrote: >> >> Please re-spin your previous patch and submit it properly. >> >> Best regards, >> Javier > > Hi all! What about stopping this meaningless discussion about resending > full patch series when everybody know how to fix is quickly in editor > (e.g with sed under 5s) and not wasting another 10 minutes to generate > new unified diff sent via SMTP protocol? > No, there is a reason why we have written rules on how patches should be submitted. Everyone in the kernel community is expected to optimize their workflow according to these rules to make life easier for people reviewing and merging the patches. As you said now someone has to fix this using an editor and that is an error prone process. Besides, why it would take 10 minutes to generate a proper patch-set? git is very good on this regard (i.e: git commit ---fixup && git rebase -i && git format-patch && git send-email). I won't argue anymore but I find very sad that people who have been in the kernel community for years don't follow the basic rules we have documented it. So I wonder why we have the documentation in the first place and how can we expect newcomers to follow if even experienced kernel hackers don't. > -- > Pali Roh?r > pali.rohar at gmail.com Best regards, Javier
next prev parent reply other threads:[~2015-04-13 8:32 UTC|newest] Thread overview: 82+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-04-02 14:38 [PATCHv3] media: i2c/adp1653: devicetree support for adp1653 Pavel Machek 2015-04-02 14:38 ` Pavel Machek 2015-04-02 16:14 ` Sakari Ailus 2015-04-02 16:14 ` Sakari Ailus 2015-04-02 16:14 ` Sakari Ailus 2015-04-02 20:30 ` Pavel Machek 2015-04-02 20:30 ` Pavel Machek 2015-04-02 20:30 ` Pavel Machek 2015-04-02 23:48 ` Sakari Ailus 2015-04-02 23:48 ` Sakari Ailus 2015-04-02 23:48 ` Sakari Ailus 2015-04-03 8:23 ` Pavel Machek 2015-04-03 8:23 ` Pavel Machek 2015-04-03 11:23 ` Sakari Ailus 2015-04-03 11:23 ` Sakari Ailus 2015-04-03 11:23 ` Sakari Ailus 2015-04-03 20:29 ` Pavel Machek 2015-04-03 20:29 ` Pavel Machek 2015-04-03 21:35 ` Sakari Ailus 2015-04-03 21:35 ` Sakari Ailus 2015-04-02 20:34 ` [PATCHv4] " Pavel Machek 2015-04-02 20:34 ` Pavel Machek 2015-04-02 20:34 ` Pavel Machek 2015-04-02 22:18 ` Javier Martinez Canillas 2015-04-02 22:18 ` Javier Martinez Canillas 2015-04-03 8:21 ` Pavel Machek 2015-04-03 8:21 ` Pavel Machek 2015-04-03 8:21 ` Pavel Machek 2015-04-03 8:49 ` Javier Martinez Canillas 2015-04-03 8:49 ` Javier Martinez Canillas 2015-04-03 14:22 ` Sebastian Reichel 2015-04-03 14:22 ` Sebastian Reichel 2015-04-03 8:33 ` [PATCHv5] " Pavel Machek 2015-04-03 8:33 ` Pavel Machek 2015-04-03 11:32 ` Sakari Ailus 2015-04-03 11:32 ` Sakari Ailus 2015-04-03 20:26 ` [PATCHv6] media: i2c/adp1653: Documentation for " Pavel Machek 2015-04-03 20:26 ` Pavel Machek 2015-04-03 21:36 ` Sakari Ailus 2015-04-03 21:36 ` Sakari Ailus 2015-04-04 7:43 ` Pavel Machek 2015-04-04 7:43 ` Pavel Machek 2015-04-04 10:24 ` Sakari Ailus 2015-04-04 10:24 ` Sakari Ailus 2015-04-04 10:24 ` Sakari Ailus 2015-04-04 17:11 ` Pavel Machek 2015-04-04 17:11 ` Pavel Machek 2015-04-04 17:11 ` Pavel Machek 2015-04-04 20:03 ` Sakari Ailus 2015-04-04 20:03 ` Sakari Ailus 2015-04-04 20:03 ` Sakari Ailus 2015-04-09 7:42 ` [PATCHv7] media: i2c/adp1653: Devicetree " Pavel Machek 2015-04-09 7:42 ` Pavel Machek 2015-04-09 9:10 ` Sebastian Reichel 2015-04-09 9:10 ` Sebastian Reichel 2015-04-09 9:10 ` Sebastian Reichel 2015-04-09 11:29 ` Pavel Machek 2015-04-09 11:29 ` Pavel Machek 2015-04-09 12:19 ` Sebastian Reichel 2015-04-09 12:19 ` Sebastian Reichel 2015-04-09 12:19 ` Sebastian Reichel 2015-04-09 12:31 ` [PATCHv7] media: i2c/adp1653: fix includes Pavel Machek 2015-04-09 12:31 ` Pavel Machek 2015-04-09 12:31 ` Pavel Machek 2015-04-09 12:43 ` Javier Martinez Canillas 2015-04-09 12:43 ` Javier Martinez Canillas 2015-04-09 12:59 ` Pali Rohár 2015-04-09 12:59 ` Pali Rohár 2015-04-09 12:59 ` Pali Rohár 2015-04-13 8:32 ` Javier Martinez Canillas [this message] 2015-04-13 8:32 ` Javier Martinez Canillas 2015-04-09 21:47 ` [PATCHv7] media: i2c/adp1653: Devicetree support for adp1653 Sakari Ailus 2015-04-09 21:47 ` Sakari Ailus 2015-04-13 13:00 ` Pavel Machek 2015-04-13 13:00 ` Pavel Machek 2015-04-13 13:00 ` Pavel Machek 2015-04-03 21:39 ` [PATCHv6] media: i2c/adp1653: Documentation for devicetree " Sakari Ailus 2015-04-03 21:39 ` Sakari Ailus 2015-04-03 21:39 ` Sakari Ailus 2015-04-03 21:04 ` [PATCHv5] media: i2c/adp1653: " Pavel Machek 2015-04-03 21:04 ` Pavel Machek 2015-04-03 21:04 ` Pavel Machek
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='CABxcv==j=GLq0o6Shr32-81-6o0z4mSMOm7c_4Q1e+rQBgdEKQ@mail.gmail.com' \ --to=javier@dowhile0.org \ --cc=aaro.koskinen@iki.fi \ --cc=akpm@osdl.org \ --cc=bcousson@baylibre.com \ --cc=devicetree@vger.kernel.org \ --cc=galak@codeaurora.org \ --cc=hverkuil@xs4all.nl \ --cc=ivo.g.dimitrov.75@gmail.com \ --cc=khilman@kernel.org \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-omap@vger.kernel.org \ --cc=m.chehab@samsung.com \ --cc=mchehab@osg.samsung.com \ --cc=pali.rohar@gmail.com \ --cc=patrikbachan@gmail.com \ --cc=pavel@ucw.cz \ --cc=sakari.ailus@iki.fi \ --cc=sre@kernel.org \ --cc=tony@atomide.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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.