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/viperboard: Delete an error message for a failed memory allocation in vprbrd_probe()
Date: Tue, 23 Jan 2018 14:05:39 +0000 [thread overview]
Message-ID: <f8900a77-eea4-d244-37e1-44d22484f826@users.sourceforge.net> (raw)
In-Reply-To: <20180123130130.powyttapsx3djawx@dell>
>> Can you please fix-up all of the patches I've NACKed and collect them
>> up with all the other MFD patches you currently have on the list and
>> send them as a single set please?
>>
>> Reviewing them one after another, is taking a lot of time and causing
>> my a great deal of pain.
There will be review efforts needed as usual. They might be more noticeable
in this case just because I sent some update suggestions also for software
modules from the directory “drivers/mfd”.
>> I am marking all of your other MFD submissions as 'read and reviewed'
>> and will not be processing any more until the are all contained in a
>> single, threaded set.
>>
>> Thank you!
>
> Also, could you change the subject lines, so they match that expected
> by the subsystem.
Do you request a resent for almost all changes from this patch series here?
Regards,
Markus
next prev parent reply other threads:[~2018-01-23 14:05 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 [this message]
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
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=f8900a77-eea4-d244-37e1-44d22484f826@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