From: SF Markus Elfring <elfring@users.sourceforge.net>
To: Lee Jones <lee.jones@linaro.org>, kernel-janitors@vger.kernel.org
Cc: LKML <linux-kernel@vger.kernel.org>,
"Lars Pöschel" <poeschel@lemonage.de>,
"Samuel Ortiz" <sameo@linux.intel.com>
Subject: Re: mfd: Patch management?
Date: Fri, 26 Jan 2018 17:28:01 +0100 [thread overview]
Message-ID: <856e9b19-2e42-a6b2-85c4-c89a81b071f8@users.sourceforge.net> (raw)
In-Reply-To: <20180126141255.7adgqjlonuvujp2x@dell>
>> I am curious if more positive feedback could evolve till then.
>> I would appreciate if a potentially needed resend for my selection
>> of update suggestions could become smaller (when reviewed steps
>> could be already integrated for example).
>
> I'm not entirely sure what you're trying to say,
> in any of your responses.
I imagine that acceptance for these changes could be influenced
also by review comments from other contributors.
> Are you using Google Translate to convert between your
> first language and English?
No.
> If you want to rebase your patches, to see what has been applied and
> what hasn't, you can use the MFD repo and its next-next branch.
https://git.kernel.org/pub/scm/linux/kernel/git/lee/mfd.git/log/?h=for-mfd-next-next
How are the chances that further update suggestions will be integrated
just because I sent them as small patch series in the threaded way?
Examples:
* tps65910: Adjustments for four function implementations
https://lkml.org/lkml/2018/1/16/313
* abx500-core: Adjustments for eight function implementations
https://lkml.org/lkml/2018/1/16/186
Regards,
Markus
next prev parent reply other threads:[~2018-01-26 16:28 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
[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 [this message]
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=856e9b19-2e42-a6b2-85c4-c89a81b071f8@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
all inboxes | Powered by JetHome®