From: Florian Eckert <fe@dev.tdt.de>
To: Lee Jones <lee@kernel.org>
Cc: Eckert.Florian@googlemail.com, gregkh@linuxfoundation.org,
jirislaby@kernel.org, pavel@ucw.cz, kabel@kernel.org,
u.kleine-koenig@pengutronix.de, m.brock@vanmierlo.com,
linux-kernel@vger.kernel.org, linux-serial@vger.kernel.org,
linux-leds@vger.kernel.org
Subject: Re: [Patch v8 0/6] ledtrig-tty: add additional tty state evaluation
Date: Wed, 06 Dec 2023 14:57:20 +0100 [thread overview]
Message-ID: <e69d088b1aedfef330eace35699670c6@dev.tdt.de> (raw)
In-Reply-To: <20231206134719.GF3375667@google.com>
On 2023-12-06 14:47, Lee Jones wrote:
> On Fri, 01 Dec 2023, Florian Eckert wrote:
>> On 2023-12-01 11:40, Lee Jones wrote:
>> > Applied, thanks!
>> >
>> > [1/6] tty: add new helper function tty_get_tiocm
>> > commit: 5d11a4709f552fa139c2439fead05daeb064a6f4
>> > [2/6] leds: ledtrig-tty: free allocated ttyname buffer on deactivate
>> > (no commit info)
>> > [3/6] leds: ledtrig-tty: change logging if get icount failed
>> > (no commit info)
>> > [4/6] leds: ledtrig-tty: replace mutex with completion
>> > (no commit info)
>> > [5/6] leds: ledtrig-tty: make rx tx activitate configurable
>> > (no commit info)
>> > [6/6] leds: ledtrig-tty: add additional line state evaluation
>> > (no commit info)
>>
>> I think that was a mistake? Patchset v9 is the correct patchset [1]?
>>
>> Thanks for applying v9 [1]
>
> It's automated. Not sure what happened now.
>
> Please check to ensure the correct set was applied.
I have checked that v9 is appled to the branch for-leds-next [1].
I can confirm that v9 patchset is applied there.
Thanks
Best regards
Florian
Links:
[1]
https://git.kernel.org/pub/scm/linux/kernel/git/lee/leds.git/log/?h=for-leds-next
prev parent reply other threads:[~2023-12-06 13:57 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-09 8:50 [Patch v8 0/6] ledtrig-tty: add additional tty state evaluation Florian Eckert
2023-11-09 8:50 ` [Patch v8 1/6] tty: add new helper function tty_get_tiocm Florian Eckert
2023-11-20 7:21 ` Jiri Slaby
2023-11-21 7:35 ` Florian Eckert
2023-11-09 8:50 ` [Patch v8 2/6] leds: ledtrig-tty: free allocated ttyname buffer on deactivate Florian Eckert
2023-11-23 14:06 ` Greg KH
2023-11-27 7:13 ` Florian Eckert
2023-11-27 8:04 ` Lee Jones
2023-11-27 8:19 ` Florian Eckert
2023-11-09 8:50 ` [Patch v8 3/6] leds: ledtrig-tty: change logging if get icount failed Florian Eckert
2023-11-23 14:08 ` Greg KH
2023-11-09 8:50 ` [Patch v8 4/6] leds: ledtrig-tty: replace mutex with completion Florian Eckert
2023-11-23 14:10 ` Greg KH
2023-11-09 8:50 ` [Patch v8 5/6] leds: ledtrig-tty: make rx tx activitate configurable Florian Eckert
2023-11-23 14:12 ` Greg KH
2023-11-09 8:50 ` [Patch v8 6/6] leds: ledtrig-tty: add additional line state evaluation Florian Eckert
2023-11-09 19:03 ` m.brock
2023-11-17 12:12 ` Lee Jones
2023-11-20 7:21 ` Florian Eckert
2023-11-21 15:23 ` Lee Jones
2023-11-22 9:50 ` Florian Eckert
2023-11-22 11:28 ` Lee Jones
2023-12-01 10:40 ` [Patch v8 0/6] ledtrig-tty: add additional tty " Lee Jones
2023-12-01 13:08 ` Florian Eckert
2023-12-06 13:47 ` Lee Jones
2023-12-06 13:57 ` Florian Eckert [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=e69d088b1aedfef330eace35699670c6@dev.tdt.de \
--to=fe@dev.tdt.de \
--cc=Eckert.Florian@googlemail.com \
--cc=gregkh@linuxfoundation.org \
--cc=jirislaby@kernel.org \
--cc=kabel@kernel.org \
--cc=lee@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=m.brock@vanmierlo.com \
--cc=pavel@ucw.cz \
--cc=u.kleine-koenig@pengutronix.de \
/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;
as well as URLs for NNTP newsgroup(s).