archive mirror
 help / color / mirror / Atom feed
From: Jakub Kicinski <>
To: Johannes Berg <>
Subject: Re: pull-request: wireless-2022-10-13
Date: Thu, 13 Oct 2022 08:32:04 -0700	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On Thu, 13 Oct 2022 12:04:51 +0200 Johannes Berg wrote:
> So as discussed previously, here are the fixes for the
> scan parsing issues. I had to create a merge commit to
> keep the stable commit IDs that we'd already used for
> communication.
> Please pull and let me know if there's any problem.

Odd, bot doesn't want to reply. Paolo pulled this a few hours ago FWIW.

  reply	other threads:[~2022-10-13 15:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-13 10:04 pull-request: wireless-2022-10-13 Johannes Berg
2022-10-13 15:32 ` Jakub Kicinski [this message]
2022-10-13 15:32 ` Jakub Kicinski
2022-10-13 16:13   ` Johannes Berg
2022-10-13 16:29     ` Jakub Kicinski

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \

* 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).