From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Sebastian Reichel <sre@kernel.org>
Cc: Kevin Hilman <khilman@kernel.org>,
Tony Lindgren <tony@atomide.com>,
Tyler Baker <tyler.baker@linaro.org>, Felipe Balbi <balbi@ti.com>,
Olof Johansson <olof@lixom.net>,
Marek Belisko <marek@goldelico.com>,
linux-omap <linux-omap@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] Revert "ARM: dts: twl4030: Add iio properties for bci subnode"
Date: Sat, 7 Nov 2015 14:40:40 +1100 [thread overview]
Message-ID: <20151107144040.2afa1228@canb.auug.org.au> (raw)
In-Reply-To: <20151107024457.GA18676@earth>
Hi Sebastian,
On Sat, 7 Nov 2015 03:44:57 +0100 Sebastian Reichel <sre@kernel.org> wrote:
>
> Is there an easy way to check this, so that I can create a cronjob
> checkin it? Having an additional automatic "your tree differs from
> linux-next" would be helpful, since that would make me search for
> the problem/a mail from Stephen.
Well,
wget -q -O- http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/plain/Next/SHA1s | sed -n 's/^battery\t\t*//p'
will get you the SHA1 of the top of your branch that I merged into the
latest release.
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
WARNING: multiple messages have this Message-ID (diff)
From: sfr@canb.auug.org.au (Stephen Rothwell)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] Revert "ARM: dts: twl4030: Add iio properties for bci subnode"
Date: Sat, 7 Nov 2015 14:40:40 +1100 [thread overview]
Message-ID: <20151107144040.2afa1228@canb.auug.org.au> (raw)
In-Reply-To: <20151107024457.GA18676@earth>
Hi Sebastian,
On Sat, 7 Nov 2015 03:44:57 +0100 Sebastian Reichel <sre@kernel.org> wrote:
>
> Is there an easy way to check this, so that I can create a cronjob
> checkin it? Having an additional automatic "your tree differs from
> linux-next" would be helpful, since that would make me search for
> the problem/a mail from Stephen.
Well,
wget -q -O- http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/plain/Next/SHA1s | sed -n 's/^battery\t\t*//p'
will get you the SHA1 of the top of your branch that I merged into the
latest release.
--
Cheers,
Stephen Rothwell sfr at canb.auug.org.au
next prev parent reply other threads:[~2015-11-07 3:40 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-06 16:13 [PATCH] Revert "ARM: dts: twl4030: Add iio properties for bci subnode" Sebastian Reichel
2015-11-06 16:13 ` Sebastian Reichel
2015-11-06 16:23 ` Felipe Balbi
2015-11-06 16:23 ` Felipe Balbi
2015-11-06 18:36 ` Kevin Hilman
2015-11-06 18:36 ` Kevin Hilman
2015-11-06 19:03 ` Tony Lindgren
2015-11-06 19:03 ` Tony Lindgren
2015-11-06 22:19 ` Stephen Rothwell
2015-11-06 22:19 ` Stephen Rothwell
2015-11-06 22:36 ` Kevin Hilman
2015-11-06 22:36 ` Kevin Hilman
2015-11-07 2:44 ` Sebastian Reichel
2015-11-07 2:44 ` Sebastian Reichel
2015-11-07 3:40 ` Stephen Rothwell [this message]
2015-11-07 3:40 ` Stephen Rothwell
2015-11-06 20:21 ` Belisko Marek
2015-11-06 20:21 ` Belisko Marek
2015-11-09 14:17 ` Tony Lindgren
2015-11-09 14:17 ` Tony Lindgren
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=20151107144040.2afa1228@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=balbi@ti.com \
--cc=khilman@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=marek@goldelico.com \
--cc=olof@lixom.net \
--cc=sre@kernel.org \
--cc=tony@atomide.com \
--cc=tyler.baker@linaro.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.