linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Michael Nosthoff" <bluez@heine.tech>
To: "Fabrice Fontaine" <fontaine.fabrice@gmail.com>
Cc: linux-bluetooth@vger.kernel.org,
	"Michael Nosthoff" <bluez@heine.tech>,
	"Michael Nosthoff" <buildroot@heine.tech>
Subject: Re: [PATCH BlueZ] tools/mesh-cfgtest: include  limits.h
Date: Wed, 16 Feb 2022 12:57:38 +0100	[thread overview]
Message-ID: <50-620ce680-7-4d762500@265872973> (raw)
In-Reply-To: <20220215225015.3568246-1-fontaine.fabrice@gmail.com>

Hi Fabrice,

On Tuesday, February 15, 2022 23:50 CET, Fabrice Fontaine <fontaine.fabrice@gmail.com> wrote:

> ---
> I'm sending back this patch as for an unknown reason, the patch sent by
> Michael in July 2021 is set as superseded in patchwork:
> https://patchwork.kernel.org/project/bluetooth/patch/20210722204923.29735-1-bluez@heine.tech
>
I had sent a v2 with an improved description. The buildbot didn't like the Commit Msg because of the too long
urls to the buildroot autobuilders. Maybe that's why it was marked as "archived" on patchwork?

https://patchwork.kernel.org/project/bluetooth/patch/20210723081039.30396-1-bluez@heine.tech/

Regards,
Michael


  parent reply	other threads:[~2022-02-16 12:05 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-15 22:50 [PATCH BlueZ] tools/mesh-cfgtest: include limits.h Fabrice Fontaine
2022-02-16  0:22 ` [BlueZ] " bluez.test.bot
2022-02-16 11:57 ` Michael Nosthoff [this message]
2022-02-16 12:35   ` [PATCH BlueZ] " Fabrice Fontaine
2022-02-16 18:34   ` Gix, Brian
  -- strict thread matches above, loose matches on Subject: below --
2021-07-22 20:49 Michael Nosthoff

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=50-620ce680-7-4d762500@265872973 \
    --to=bluez@heine.tech \
    --cc=buildroot@heine.tech \
    --cc=fontaine.fabrice@gmail.com \
    --cc=linux-bluetooth@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;
as well as URLs for NNTP newsgroup(s).