[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <2025021328-limes-hacking-2ddc@gregkh>
Date: Thu, 13 Feb 2025 11:13:14 +0100
From: Greg KH <gregkh@...uxfoundation.org>
To: Hsin-chen Chuang <chharry@...gle.com>
Cc: linux-bluetooth@...r.kernel.org, luiz.dentz@...il.com,
chromeos-bluetooth-upstreaming@...omium.org,
Hsin-chen Chuang <chharry@...omium.org>,
Johan Hedberg <johan.hedberg@...il.com>,
Marcel Holtmann <marcel@...tmann.org>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v4 3/3] Bluetooth: Add ABI doc for sysfs isoc_alt
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@...uxfoundation.org> wrote:
> >
> > On Thu, Feb 13, 2025 at 11:44:01AM +0800, Hsin-chen Chuang wrote:
> > > From: Hsin-chen Chuang <chharry@...omium.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
Powered by blists - more mailing lists