From: SF Markus Elfring <elfring@users.sourceforge.net>
To: Lee Jones <lee.jones@linaro.org>
Cc: kernel-janitors@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>,
"Lars Pöschel" <poeschel@lemonage.de>,
"Samuel Ortiz" <sameo@linux.intel.com>
Subject: Re: mfd: Patch management?
Date: Tue, 23 Jan 2018 16:49:59 +0000 [thread overview]
Message-ID: <4b525322-424d-328b-a348-626a26da8f61@users.sourceforge.net> (raw)
In-Reply-To: <20180123163130.h6ygmzig7syafxbh@dell>
> What I should do really is ask you to take all similar (remove error
> message, don't use sizeof(struct X), remove '= NULL') changes and
> squash them into single patches.
I would try such an approach more often if I would get also more
promising indications of corresponding change acceptance besides
other software development “surprises”.
> However, I realise that you might want the "upstream creds",
> so I won't do that
I find this view interesting somehow.
> -- but not at the expense of my time/effort.
>
> The two choices are to squash or to create a set.
This information triggers recurring difficulties around differences
in the preferred patch granularity.
Regards,
Markus
next prev parent reply other threads:[~2018-01-23 16:49 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-16 16:42 [PATCH] mfd/viperboard: Delete an error message for a failed memory allocation in vprbrd_probe() SF Markus Elfring
2018-01-23 12:58 ` Lee Jones
2018-01-23 13:01 ` Lee Jones
2018-01-23 14:05 ` SF Markus Elfring
2018-01-23 15:14 ` Lee Jones
2018-01-23 15:56 ` mfd: Patch management? SF Markus Elfring
2018-01-23 16:31 ` Lee Jones
2018-01-23 16:49 ` SF Markus Elfring [this message]
[not found] ` <49873902-c947-468d-094a-4ac175850116@users.sourceforge.net>
2018-01-26 11:45 ` Lee Jones
[not found] ` <c6e799c3-e118-20a1-3a9f-72950a080d03@users.sourceforge.net>
2018-01-26 14:12 ` Lee Jones
2018-01-26 16:28 ` SF Markus Elfring
2018-01-29 9:35 ` Lee Jones
2018-01-29 10:15 ` SF Markus Elfring
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=4b525322-424d-328b-a348-626a26da8f61@users.sourceforge.net \
--to=elfring@users.sourceforge.net \
--cc=kernel-janitors@vger.kernel.org \
--cc=lee.jones@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=poeschel@lemonage.de \
--cc=sameo@linux.intel.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