From: Sudeep Holla <sudeep.holla@arm.com>
To: Olof Johansson <olof@lixom.net>
Cc: Arnd Bergmann <arnd@arndb.de>, Kevin Hilman <khilman@kernel.org>,
SoC Team <soc@kernel.org>, ARM SoC Team <arm@kernel.org>,
Sudeep Holla <sudeep.holla@arm.com>,
ALKML <linux-arm-kernel@lists.infradead.org>
Subject: Re: [GIT PULL v2] firmware: arm_scmi: fix for v5.5
Date: Mon, 18 Nov 2019 10:31:58 +0000 [thread overview]
Message-ID: <20191118103158.GA31493@bogus> (raw)
In-Reply-To: <20191116233452.cypff3abhvifw7hl@localhost>
On Sat, Nov 16, 2019 at 03:34:52PM -0800, Olof Johansson wrote:
> On Thu, Nov 14, 2019 at 04:45:55PM +0000, Sudeep Holla wrote:
> > Hi ARM SoC Team,
> >
> > Stephen Rothwell reported issue[1] with fixes tag in the commit. I have
> > fixed the same and re-tagged it. Please drop the earlier PR and use
> > this one based on your preference(I am not sure if want to ignore or
> > fix it). Sorry for the silly mistake.
>
> Usually we don't re-merge once we pick something up, but in this case it's at
> the top of the branch so I did rebase with this version.
>
I understand, thanks. Sorry for the trouble.
> We should be running linters on the pull requests in patchwork so this is
> caught before we merge, it's on the todo list but not done yet.
>
I think even checkpatch reports such issues, I must have ignored it by
accident. I will be more careful in the future.
--
Regards,
Sudeep
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2019-11-18 10:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-13 18:04 [GIT PULL] firmware: arm_scmi: fix for v5.5 Sudeep Holla
2019-11-14 16:45 ` [GIT PULL v2] " Sudeep Holla
2019-11-16 23:34 ` Olof Johansson
2019-11-18 10:31 ` Sudeep Holla [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=20191118103158.GA31493@bogus \
--to=sudeep.holla@arm.com \
--cc=arm@kernel.org \
--cc=arnd@arndb.de \
--cc=khilman@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=olof@lixom.net \
--cc=soc@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.