Linux kernel -stable discussions
 help / color / mirror / Atom feed
From: Jiri Slaby <jirislaby@kernel.org>
To: Sasha Levin <sashal@kernel.org>
Cc: stable@vger.kernel.org, stable-commits@vger.kernel.org,
	ilpo.jarvinen@linux.intel.com,
	Rodolfo Giometti <giometti@enneenne.com>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	"David S. Miller" <davem@davemloft.net>
Subject: Re: Patch "tty/serial: Make ->dcd_change()+uart_handle_dcd_change() status bool active" has been added to the 6.1-stable tree
Date: Thu, 24 Oct 2024 08:31:42 +0200	[thread overview]
Message-ID: <11f81797-0452-47dd-b49f-9466110a6781@kernel.org> (raw)
In-Reply-To: <ZxjidR9PG2vfB_De@sashalap>

On 23. 10. 24, 13:48, Sasha Levin wrote:
> On Wed, Oct 23, 2024 at 08:25:12AM +0200, Jiri Slaby wrote:
>> On 22. 10. 24, 19:54, Sasha Levin wrote:
>>> This is a note to let you know that I've just added the patch titled
>>>
>>>     tty/serial: Make ->dcd_change()+uart_handle_dcd_change() status 
>>> bool active
>>
>> This is a cleanup, not needed in stable. (Unless something context- 
>> depends on it.)
> 
> The 3 commits you've pointed out are a pre-req for 30c9ae5ece8e ("xhci:
> dbc: honor usb transfer size boundaries.").

Ah, OK, thanks.

And OMG (side note), the patch reintroduced the non-sense pattern I 
removed (the added kfifo_len()).




But re. this patch
   0388a152fc55 tty/serial: Make ->dcd_change()+uart_handle_dcd_change() 
status bool active
with
   Stable-dep-of: 40d7903386df ("serial: imx: Update mctrl old_status on 
RTSD interrupt")

I fail to see how is that a dep?

thanks,
-- 
js
suse labs

      parent reply	other threads:[~2024-10-24  6:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20241022175403.2844928-1-sashal@kernel.org>
2024-10-23  6:25 ` Patch "tty/serial: Make ->dcd_change()+uart_handle_dcd_change() status bool active" has been added to the 6.1-stable tree Jiri Slaby
2024-10-23 11:48   ` Sasha Levin
2024-10-23 11:56     ` Ilpo Järvinen
2024-10-23 14:20       ` Sasha Levin
2024-10-23 14:24         ` Ilpo Järvinen
2024-10-24  6:31     ` Jiri Slaby [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=11f81797-0452-47dd-b49f-9466110a6781@kernel.org \
    --to=jirislaby@kernel.org \
    --cc=davem@davemloft.net \
    --cc=giometti@enneenne.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=ilpo.jarvinen@linux.intel.com \
    --cc=sashal@kernel.org \
    --cc=stable-commits@vger.kernel.org \
    --cc=stable@vger.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