From: Darren Hart <dvhart@infradead.org>
To: "Michał Kępień" <kernel@kempniu.pl>
Cc: Jonathan Woithe <jwoithe@just42.net>,
Andy Shevchenko <andy@infradead.org>,
platform-driver-x86@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/3] fujitsu-laptop: call_fext_func() cleanup
Date: Wed, 5 Apr 2017 08:29:02 -0700 [thread overview]
Message-ID: <20170405152902.GB27833@fury> (raw)
In-Reply-To: <20170405065023.3267-1-kernel@kempniu.pl>
On Wed, Apr 05, 2017 at 08:50:20AM +0200, Michał Kępień wrote:
> This series contains a few cleanups for the call_fext_func() function.
> Just as a reminder, please note that v1 of this series is currently
> applied in testing.
>
> Changes from v1:
>
> - Update debug message logged by call_fext_func() to reflect code flow
> changes introduced by patch 2/3.
My apologies Michał, I misunderstood - I was thinking you had a second change to
the 11 patch series, so I asked for a v2.
This series is already in for-next, and we only rebase that for bugs that would
be bad to leave in the history - like things that break bisecting.
For this change, would you please send just 1 new patch on top of for-next?
Again, I'm sorry that, my fault.
--
Darren Hart
VMware Open Source Technology Center
next prev parent reply other threads:[~2017-04-05 15:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-05 6:50 [PATCH v2 0/3] fujitsu-laptop: call_fext_func() cleanup Michał Kępień
2017-04-05 6:50 ` [PATCH v2 1/3] platform/x86: fujitsu-laptop: clean up local variables in call_fext_func() Michał Kępień
2017-04-05 6:50 ` [PATCH v2 2/3] platform/x86: fujitsu-laptop: simplify call_fext_func() Michał Kępień
2017-04-05 6:50 ` [PATCH v2 3/3] platform/x86: fujitsu-laptop: rename call_fext_func() arguments Michał Kępień
2017-04-05 15:29 ` Darren Hart [this message]
2017-04-05 19:46 ` [PATCH v2 0/3] fujitsu-laptop: call_fext_func() cleanup Michał Kępień
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=20170405152902.GB27833@fury \
--to=dvhart@infradead.org \
--cc=andy@infradead.org \
--cc=jwoithe@just42.net \
--cc=kernel@kempniu.pl \
--cc=linux-kernel@vger.kernel.org \
--cc=platform-driver-x86@vger.kernel.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