From: Arnd Bergmann <arnd@arndb.de>
To: linux-arm-kernel@lists.infradead.org
Cc: Barry Song <21cnbao@gmail.com>,
Daniel Lezcano <daniel.lezcano@linaro.org>,
Yanchang Li <yl22@csr.com>, LKML <linux-kernel@vger.kernel.org>,
DL-SHA-WorkGroupLinux <workgroup.linux@csr.com>,
Barry Song <Baohua.Song@csr.com>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [PATCH] clocksource: sirf: remove unused variable
Date: Tue, 13 Jan 2015 17:22:55 +0100 [thread overview]
Message-ID: <8635006.m811OQopQd@wuerfel> (raw)
In-Reply-To: <CAGsJ_4xgF5y9GQ2roh1MYSrvm+_n+fyxsUiVCp4gm+igTbdWdQ@mail.gmail.com>
On Tuesday 13 January 2015 23:24:24 Barry Song wrote:
>
> yes, arnd. i also asked Daniel to apply "clocksource: marco: Rename
> marco to atlas7" rebased on this fix here:
> https://git.linaro.org/people/daniel.lezcano/linux.git/commit/81428bbe1d8a073bb3741678ef1d3c1016119c77
Ok
> so this one is excluded from my pull request for atlas7. a
> pull-request from arm-soc might cause merge conflicts?
I was just doing build-tests on linux-next today and submitted patches
for each new warning or error I saw. Nothing to worry about as it's already
fixed and I'm dropping my version as soon as the other fix makes it into
next.
Arnd
next prev parent reply other threads:[~2015-01-13 16:23 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-13 14:22 [PATCH] clocksource: sirf: remove unused variable Arnd Bergmann
2015-01-13 14:27 ` Daniel Lezcano
2015-01-13 15:24 ` Arnd Bergmann
2015-01-13 15:39 ` Daniel Lezcano
2015-01-13 15:24 ` Barry Song
2015-01-13 16:22 ` Arnd Bergmann [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-12-23 21:33 [PATCH] clocksource: sirf: Remove " Fabio Estevam
2015-01-11 14:45 ` Barry Song
2014-12-15 15:59 Thierry Reding
2014-12-15 16:17 ` Daniel Lezcano
2015-01-11 15:58 ` Barry Song
2015-01-11 20:51 ` Daniel Lezcano
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=8635006.m811OQopQd@wuerfel \
--to=arnd@arndb.de \
--cc=21cnbao@gmail.com \
--cc=Baohua.Song@csr.com \
--cc=daniel.lezcano@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=workgroup.linux@csr.com \
--cc=yl22@csr.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