From: Jacek Anaszewski <j.anaszewski@samsung.com>
To: linz@li-pro.net
Cc: linux-leds@vger.kernel.org, linux-ide@vger.kernel.org,
"Joseph Jezak" <josejx@gentoo.org>,
"Nico Macrionitis" <acrux@cruxppc.org>,
"Jörg Sommer" <joerg@alea.gnuu.de>,
"Richard Purdie" <rpurdie@rpsys.net>, "Tejun Heo" <tj@kernel.org>,
"David S. Miller" <davem@davemloft.net>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 1/7] leds: convert IDE trigger to common disk trigger
Date: Tue, 21 Jun 2016 09:13:59 +0200 [thread overview]
Message-ID: <5768E937.80206@samsung.com> (raw)
In-Reply-To: <57686003.7030100@li-pro.net>
Hi Stephan,
On 06/20/2016 11:28 PM, Stephan Linz wrote:
> Hi Jacek,
>
> thanks a lot. Can you tell me, when the LED for-next branch will merge
> into mainline?
If everything will go as usually then the merge window will start
in four weeks.
Best regards,
Jacek Anaszewski
prev parent reply other threads:[~2016-06-21 7:46 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-08 22:29 Stephan Linz
2016-06-08 22:29 ` [PATCH v3 2/7] leds: documentation: 'ide-disk' to 'disk-activity' Stephan Linz
2016-06-21 15:05 ` Mark Rutland
2016-06-22 7:55 ` Jacek Anaszewski
2016-06-22 10:16 ` Mark Rutland
2016-06-22 16:05 ` Stephan Linz
2016-06-23 6:40 ` Jacek Anaszewski
2016-06-23 19:38 ` [PATCH v5] " Stephan Linz
2016-06-24 6:50 ` Jacek Anaszewski
2016-06-24 17:18 ` Stephan Linz
2016-06-08 22:29 ` [PATCH v3 3/7] powerpc: use the new LED disk activity trigger Stephan Linz
2016-06-08 22:29 ` [PATCH v3 4/7] arm: " Stephan Linz
2016-06-09 7:18 ` Gregory CLEMENT
2016-06-08 22:29 ` [PATCH v3 5/7] mips: " Stephan Linz
2016-06-08 22:29 ` [PATCH v3 6/7] parisc: " Stephan Linz
2016-06-08 22:29 ` [PATCH v3 7/7] unicore32: " Stephan Linz
2016-06-09 7:29 ` [PATCH v3 1/7] leds: convert IDE trigger to common disk trigger Jacek Anaszewski
2016-06-09 22:27 ` Stephan Linz
2016-06-20 8:36 ` Jacek Anaszewski
2016-06-20 21:28 ` Stephan Linz
2016-06-21 7:13 ` Jacek Anaszewski [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=5768E937.80206@samsung.com \
--to=j.anaszewski@samsung.com \
--cc=acrux@cruxppc.org \
--cc=davem@davemloft.net \
--cc=joerg@alea.gnuu.de \
--cc=josejx@gentoo.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=linz@li-pro.net \
--cc=rpurdie@rpsys.net \
--cc=tj@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
Powered by JetHome