From: Jacek Anaszewski <j.anaszewski@samsung.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: torvalds@linux-foundation.org, linux-kernel@vger.kernel.org,
linux-leds@vger.kernel.org, amitoj1606@gmail.com, ao2@ao2.it,
drivshin@allworx.com, geert+renesas@glider.be,
hkallweit1@gmail.com, stefan.wahren@i2se.com,
yongjun_wei@trendmicro.com.cn
Subject: Re: [GIT PULL] LED subsystem updates for 4.6
Date: Tue, 15 Mar 2016 08:51:04 +0100 [thread overview]
Message-ID: <56E7BEE8.2000004@samsung.com> (raw)
In-Reply-To: <20160315103613.3eb6347e@canb.auug.org.au>
Hi Stephen,
On 03/15/2016 12:36 AM, Stephen Rothwell wrote:
> Hi Jacek,
>
> On Mon, 14 Mar 2016 11:24:57 +0100 Jacek Anaszewski <j.anaszewski@samsung.com> wrote:
>>
>> Please pull LED updates for 4.6 merge cycle.
>>
>> The following changes since commit b562e44f507e863c6792946e4e1b1449fbbac85d:
>>
>> Linux 4.5 (2016-03-13 21:28:54 -0700)
>>
>> are available in the git repository at:
>>
>> git://git.kernel.org/pub/scm/linux/kernel/git/j.anaszewski/linux-leds.git tags/leds_for_4.6
>>
>> for you to fetch changes up to 7296c33ed12ef13de50e03c76643382123766f96:
>>
>> leds: triggers: simplify led_trigger_store (2016-03-14 09:22:23 +0100)
>
> All rebased since yesterday for some reason?
>
I just wanted to make sure that no unexpected problem has occurred
after rebasing onto 4.5 release. Is it in some way more advantageous to
base a pull request on rc7, than on a final release?
--
Best regards,
Jacek Anaszewski
next prev parent reply other threads:[~2016-03-15 7:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-14 10:24 [GIT PULL] LED subsystem updates for 4.6 Jacek Anaszewski
2016-03-14 23:36 ` Stephen Rothwell
2016-03-15 7:51 ` Jacek Anaszewski [this message]
2016-03-16 5:04 ` Linus Torvalds
2016-03-16 7:40 ` Jacek Anaszewski
2016-03-16 5:15 ` Linus Torvalds
2016-03-16 7:47 ` Jacek Anaszewski
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=56E7BEE8.2000004@samsung.com \
--to=j.anaszewski@samsung.com \
--cc=amitoj1606@gmail.com \
--cc=ao2@ao2.it \
--cc=drivshin@allworx.com \
--cc=geert+renesas@glider.be \
--cc=hkallweit1@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=stefan.wahren@i2se.com \
--cc=torvalds@linux-foundation.org \
--cc=yongjun_wei@trendmicro.com.cn \
/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.