From: Krzysztof Kozlowski <krzk@kernel.org>
To: Dan Murphy <dmurphy@ti.com>
Cc: sre@kernel.org, pali@kernel.org, linux-pm@vger.kernel.org,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2/2] power: bq27xxx: Fix spacing style and white space issues
Date: Wed, 9 Sep 2020 08:32:39 +0200 [thread overview]
Message-ID: <CAJKOXPd86EWCLb8di5FDmFn-W0MPJQNgJUa8QhURbps4_byf1Q@mail.gmail.com> (raw)
In-Reply-To: <b9db96d3-c94e-79b2-006b-eb7ae90de1b3@ti.com>
On Tue, 8 Sep 2020 at 22:44, Dan Murphy <dmurphy@ti.com> wrote:
>
> Krzysztof
>
> On 9/8/20 3:32 PM, Krzysztof Kozlowski wrote:
> > On Thu, 30 Jul 2020 at 16:32, Dan Murphy <dmurphy@ti.com> wrote:
> >> Fix spacing style issues with the chip data array. As well as fix
> >> missing new line after variable declaration.
> >>
> >> Signed-off-by: Dan Murphy <dmurphy@ti.com>
> >> ---
> >> drivers/power/supply/bq27xxx_battery.c | 63 ++++++++++++++------------
> >> 1 file changed, 33 insertions(+), 30 deletions(-)
> > Hi all,
> >
> > Different topic. Do you know what is happening with Andrew's email? I
> > receive bounces with 550, so permanent error (no recipient under this
> > address).
>
> Andrews email is invalid. He no longer works for TI.
Thanks for update. Does he plan to send an email update? If not, I can
just remove him from MAINTAINERS.
Best Regards,
Krzysztof
prev parent reply other threads:[~2020-09-09 6:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-30 14:31 [PATCH 1/2] power: bq27xxx: Update to SPDX licensing Dan Murphy
2020-07-30 14:31 ` [PATCH 2/2] power: bq27xxx: Fix spacing style and white space issues Dan Murphy
2020-07-30 15:25 ` Andrew F. Davis
2020-07-30 15:35 ` Dan Murphy
2020-09-08 20:32 ` Krzysztof Kozlowski
2020-09-08 20:44 ` Dan Murphy
2020-09-09 6:32 ` Krzysztof Kozlowski [this message]
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=CAJKOXPd86EWCLb8di5FDmFn-W0MPJQNgJUa8QhURbps4_byf1Q@mail.gmail.com \
--to=krzk@kernel.org \
--cc=dmurphy@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=pali@kernel.org \
--cc=sre@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;
as well as URLs for NNTP newsgroup(s).