From: Greg KH <gregkh@linuxfoundation.org>
To: Hsin-chen Chuang <chharry@google.com>
Cc: linux-bluetooth@vger.kernel.org, luiz.dentz@gmail.com,
chromeos-bluetooth-upstreaming@chromium.org,
Hsin-chen Chuang <chharry@chromium.org>,
Johan Hedberg <johan.hedberg@gmail.com>,
Marcel Holtmann <marcel@holtmann.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 3/3] Bluetooth: Add ABI doc for sysfs isoc_alt
Date: Thu, 13 Feb 2025 11:13:14 +0100 [thread overview]
Message-ID: <2025021328-limes-hacking-2ddc@gregkh> (raw)
In-Reply-To: <CADg1FFc9_QH10UqxGqjf8hnJkHWjhy6EMPrfDCgvBx2OdOydLg@mail.gmail.com>
On Thu, Feb 13, 2025 at 06:07:59PM +0800, Hsin-chen Chuang wrote:
> On Thu, Feb 13, 2025 at 6:01 PM Greg KH <gregkh@linuxfoundation.org> wrote:
> >
> > On Thu, Feb 13, 2025 at 11:44:01AM +0800, Hsin-chen Chuang wrote:
> > > From: Hsin-chen Chuang <chharry@chromium.org>
> > >
> > > The functionality was completed in commit c04f2e4f4ea1 ("Bluetooth: Fix
> > > possible race with userspace of sysfs isoc_alt")
> > >
> > > Fixes: c04f2e4f4ea1 ("Bluetooth: Fix possible race with userspace of sysfs isoc_alt")
> >
> > Where is this git id? I don't see it in linux-next, are you sure it is
> > correct?
>
> This hash is the first patch of this series.
That's not a valid git id as it only exists on your local system and no
where else :(
> So I guess I should send this patch after the ancestors are all
> applied then.
Or better yet, include the api addition as part of the patch that
actually adds the new api.
thanks,
greg k-h
next prev parent reply other threads:[~2025-02-13 10:13 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-13 3:43 [PATCH v4 1/3] Bluetooth: Fix possible race with userspace of sysfs isoc_alt Hsin-chen Chuang
2025-02-13 3:44 ` [PATCH v4 2/3] Bluetooth: Always allow SCO packets for user channel Hsin-chen Chuang
2025-02-13 3:44 ` [PATCH v4 3/3] Bluetooth: Add ABI doc for sysfs isoc_alt Hsin-chen Chuang
2025-02-13 10:01 ` Greg KH
2025-02-13 10:07 ` Hsin-chen Chuang
2025-02-13 10:13 ` Greg KH [this message]
2025-02-13 10:14 ` Hsin-chen Chuang
2025-02-13 4:34 ` [v4,1/3] Bluetooth: Fix possible race with userspace of " bluez.test.bot
2025-02-13 10:01 ` [PATCH v4 1/3] " Greg KH
2025-02-13 11:57 ` Hsin-chen Chuang
2025-02-13 12:10 ` Greg KH
2025-02-13 13:33 ` Hsin-chen Chuang
2025-02-13 13:45 ` Greg KH
2025-02-13 14:06 ` Hsin-chen Chuang
2025-02-13 14:22 ` Luiz Augusto von Dentz
2025-02-13 14:35 ` Greg KH
2025-02-13 15:56 ` Luiz Augusto von Dentz
2025-02-13 16:05 ` Greg KH
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=2025021328-limes-hacking-2ddc@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=chharry@chromium.org \
--cc=chharry@google.com \
--cc=chromeos-bluetooth-upstreaming@chromium.org \
--cc=johan.hedberg@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.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