public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Christian Eggers <ceggers@arri.de>
Cc: Luiz Augusto von Dentz <luiz.dentz@gmail.com>,
	linux-bluetooth@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH 6.6.y] Bluetooth: HCI: Set extended advertising data synchronously
Date: Wed, 9 Jul 2025 08:19:52 +0200	[thread overview]
Message-ID: <2025070935-curdle-policy-9559@gregkh> (raw)
In-Reply-To: <22184570.4csPzL39Zc@n9w6sw14>

On Tue, Jul 08, 2025 at 11:14:59PM +0200, Christian Eggers wrote:
> > > You made major changes here from the upstream version, PLEASE document
> > > them properly in the changelog.  Also, can you test it to verify that it
> > > works and doesn't blow up the stack like I'm guessing it might?
> 
> @Greg: The only reason for the "differences" between the mainline and the 6.6
> version of the patch is, that the existing code I had to move up within 
> hci_sync.c differs between these kernels. The actual modifications I made,
> should be the same. Is this something I shall document in the changelog
> (and resend the patch)?

Yes please.

thanks,

greg k-h

  reply	other threads:[~2025-07-09  6:19 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <2025070625-wafer-speed-20c1@gregkh>
2025-07-07  8:02 ` [PATCH 6.6.y] Bluetooth: HCI: Set extended advertising data synchronously Christian Eggers
2025-07-07  8:11   ` Greg KH
2025-07-07  8:24   ` [6.6.y] " bluez.test.bot
2025-07-07  8:13 ` [PATCH 6.6.y] " Christian Eggers
2025-07-08 15:36   ` Greg KH
2025-07-08 15:56     ` Luiz Augusto von Dentz
2025-07-08 21:14       ` Christian Eggers
2025-07-09  6:19         ` Greg KH [this message]
2025-07-09  9:05 ` [PATCH 6.6.y v2] " Christian Eggers
2025-07-09  9:20   ` [6.6.y,v2] " bluez.test.bot

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=2025070935-curdle-policy-9559@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=ceggers@arri.de \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=luiz.dentz@gmail.com \
    --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