All of lore.kernel.org
 help / color / mirror / Atom feed
From: "VAUTRIN Emmanuel (Canal Plus Prestataire)" <Emmanuel.VAUTRIN@cpexterne.org>
To: "connman@lists.linux.dev" <connman@lists.linux.dev>
Subject: RE: [PATCH] iwd: Fix station in scan callback
Date: Tue, 18 Jan 2022 10:39:34 +0000	[thread overview]
Message-ID: <MRZP264MB1544DC10A3C17E1934D4CF0893589@MRZP264MB1544.FRAP264.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <MRZP264MB15441C964067460C12EC95B793589@MRZP264MB1544.FRAP264.PROD.OUTLOOK.COM>

The station shall be searched in stations table instead of networks.
Fixes: 8371114aaef9 ("iwd: Hookup manual scan trigger")
---
 plugins/iwd.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/plugins/iwd.c b/plugins/iwd.c
index b0e17a4d6396..bb97262eff38 100644
--- a/plugins/iwd.c
+++ b/plugins/iwd.c
@@ -555,7 +555,7 @@ static void cm_device_scan_cb(DBusMessage *message, void *user_data)
 	const char *path = user_data;
 	struct iwd_station *iwds;
 
-	iwds = g_hash_table_lookup(networks, path);
+	iwds = g_hash_table_lookup(stations, path);
 	if (!iwds)
 		return;
 
-- 
2.25.1
Hi Daniel,

I wish you a happy new year!
It seems that I am still accountering the tabs -> spaces issue.
I try to send the patch back in the message.

Best Regards,

Emmanuel

  parent reply	other threads:[~2022-01-18 10:39 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20220118102842.1199829-1-Emmanuel.VAUTRIN@cpexterne.org>
2022-01-18 10:33 ` [PATCH] iwd: Fix station in scan callback VAUTRIN Emmanuel (Canal Plus Prestataire)
2022-01-18 10:38   ` Michael Nazzareno Trimarchi
2022-01-18 10:47     ` VAUTRIN Emmanuel (Canal Plus Prestataire)
2022-01-18 10:39   ` VAUTRIN Emmanuel (Canal Plus Prestataire) [this message]
2022-01-21  7:48     ` Daniel Wagner
2022-01-21  9:47       ` VAUTRIN Emmanuel (Canal Plus Prestataire)

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=MRZP264MB1544DC10A3C17E1934D4CF0893589@MRZP264MB1544.FRAP264.PROD.OUTLOOK.COM \
    --to=emmanuel.vautrin@cpexterne.org \
    --cc=connman@lists.linux.dev \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.