From: Sebastian Reichel <sre@kernel.org>
To: Liam Breck <liam@networkimprov.net>
Cc: linux-pm@vger.kernel.org, Tony Lindgren <tony@atomide.com>,
"Mark A . Greer" <mgreer@animalcreek.com>,
Liam Breck <kernel@networkimprov.net>,
Matt Ranostay <matt@ranostay.consulting>
Subject: Re: [PATCH v3 0/6] BQ24190 charger fixes
Date: Tue, 17 Jan 2017 18:06:39 +0100 [thread overview]
Message-ID: <20170117170639.uoy6ulpnbilg35pz@earth> (raw)
In-Reply-To: <CAKvHMgSEimsV7+VbqQi8Ex-ztqLCJbKQ7DD_NucyRB0bP5L4+g@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1429 bytes --]
Hi,
On Mon, Jan 16, 2017 at 10:01:34PM -0800, Liam Breck wrote:
> On Mon, Jan 16, 2017 at 7:26 PM, Sebastian Reichel <sre@kernel.org> wrote:
> > On Mon, Jan 16, 2017 at 06:28:28PM -0800, Liam Breck wrote:
> >> These are misc fixes, tested on a custom OMAP3 board.
> >>
> >> Changes in v3
> >>
> >> #1 fixes figure ID to 37
> >> #5 fixes line over 80 chars
> >> #* adds Acked-by Tony & Mark
> >
> > You forgot to fix the whitespace issues Mark mentioned, also
> > please use "git send-mail" or make sure, that your patchset
> > is threaded (patch 1-6 are replies to "patch" 0) and the
> > actual patch is inline and can be applied using "git am"
> > (which currently complains).
>
> Hi, would you accept the v3 patches as-is were I the module
> maintainer? Because I am the de facto maintainer :-)
>
> I contracted Mark to write this driver, and he hasn't had hardware on
> which to test it for a few years...
So I mentioned three issues:
- Mail Threading
Please *always* do this on kernel mailinglists. Otherwise
other unrelated patches might be in between your patch series.
- MIME Patches
Your patches do not apply. See also Section 6 in
in Documentation/process/submitting-patches.rst
- Whitespace Issue
If you do style changes, do them in a separate patch. If you
move this new patch to the end of the series, I can apply the
other ones directly.
-- Sebastian
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2017-01-17 17:06 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-17 2:28 [PATCH v3 0/6] BQ24190 charger fixes Liam Breck
2017-01-17 3:26 ` Sebastian Reichel
2017-01-17 6:01 ` Liam Breck
2017-01-17 17:06 ` Sebastian Reichel [this message]
2017-01-18 17:26 ` [PATCH v4 0/7] " Liam Breck
2017-01-18 17:26 ` [PATCH v4 1/7] power: bq24190_charger: Fix irq trigger to IRQF_TRIGGER_FALLING Liam Breck
2017-01-18 17:26 ` [PATCH v4 2/7] power: bq24190_charger: Call set_mode_host() on pm_resume() Liam Breck
2017-01-18 17:26 ` [PATCH v4 3/7] power: bq24190_charger: Install irq_handler_thread() at end of probe() Liam Breck
2017-01-18 17:26 ` [PATCH v4 4/7] power: bq24190_charger: Adjust formatting Liam Breck
2017-01-18 17:26 ` [PATCH v4 5/7] power: bq24190_charger: Call power_supply_changed() for relevant component Liam Breck
2017-01-18 17:26 ` [PATCH v4 6/7] power: bq24190_charger: Don't read fault register outside irq_handle_thread() Liam Breck
2017-01-18 17:26 ` [PATCH v4 7/7] power: bq24190_charger: Handle fault before status on interrupt Liam Breck
2017-01-20 11:51 ` [PATCH v4 0/7] BQ24190 charger fixes Sebastian Reichel
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=20170117170639.uoy6ulpnbilg35pz@earth \
--to=sre@kernel.org \
--cc=kernel@networkimprov.net \
--cc=liam@networkimprov.net \
--cc=linux-pm@vger.kernel.org \
--cc=matt@ranostay.consulting \
--cc=mgreer@animalcreek.com \
--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: 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