Received: by 2002:a25:ad19:0:0:0:0:0 with SMTP id y25csp548387ybi; Fri, 12 Jul 2019 00:33:19 -0700 (PDT) X-Google-Smtp-Source: APXvYqxHmB+MxDop8p3kmpR5t5YbkH9iKfj5K0xi5TXC4zUXOfZ9i2VrHkPsnsidKeRdaPdEiV65 X-Received: by 2002:a17:90a:8984:: with SMTP id v4mr9871736pjn.133.1562916799421; Fri, 12 Jul 2019 00:33:19 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1562916799; cv=none; d=google.com; s=arc-20160816; b=LBJdnJf/DgwBB7B9NNXk5u0jEehGDK8dQXCIQfLdUN406u+hhIafLV/H7AuuzEHLUO tXlpEIsTmHDWV6+kiq5s/2WG94oBhA8ZDZO97SZQvFS776UuPXchM2dAgaFznO4RKZ+X FK2P4HTVTuB+82MbFw8Q8t8NhtLm7205dOg/PLOMXRAWqKA23KX0/7NFrhFnscHBMddi W4mVnxh7lpysmfI/c7lyEunyBIbjPNfLbJEb+XN9MnTwdJ6kN5sgNe0RO/hrlpCKqdyc iKaOGr0cE9fx/2QArlMJ9BqFsMWJW7/clD8ga1dQpk57hmSofdJmSJ0iQdKAA9L2lcbU uCkA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :references:in-reply-to:date:cc:to:from:subject:message-id; bh=cMGtXAyVwaAHLwd2X5QW5aXd3ZOk841ksGCk7jfvNf0=; b=pek3koJMm0ZaLm1ZAhcA+RMq7vnitcePlot1BuejGlESLrRXGbPfWJ1fSwyNexpDyK vdqWaVLn2URaBMckAsdgwJ3BJPFmUpYUuw6tcrDGZ0PggwUzm+wVL6Qr2HQxbV59QDTk iwYY5MAF1XTXOaacVNV1xMv1OC71nEMoX6hUSyhzNL83ln7H+sghySvFwEyVKSxEqDMz +8D/PVbQqpIKk0GqwAIMjisqrIfDMvZ1tcTwyQ/a4j8OMbdS/5tXWQ8XMJeArpEkJaTT NMSPyKh/TjaxSIQPXVIFik5arOz3MebA1sutgzIoJIpCSmrXAmEcIFyxyd69SBVA+8wZ oDlw== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-wireless-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-wireless-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id o33si7013644plb.408.2019.07.12.00.33.03; Fri, 12 Jul 2019 00:33:19 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-wireless-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-wireless-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-wireless-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726057AbfGLHb4 (ORCPT + 99 others); Fri, 12 Jul 2019 03:31:56 -0400 Received: from s3.sipsolutions.net ([144.76.43.62]:54046 "EHLO sipsolutions.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726033AbfGLHb4 (ORCPT ); Fri, 12 Jul 2019 03:31:56 -0400 Received: by sipsolutions.net with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1hlq26-0004rt-TH; Fri, 12 Jul 2019 09:31:54 +0200 Message-ID: <86bc79ccd379497d56bade79ec8f717603110ef7.camel@sipsolutions.net> Subject: Re: [PATCH v2 05/16] wilc1000: add wilc_wlan_cfg.c From: Johannes Berg To: Ajay.Kathat@microchip.com, linux-wireless@vger.kernel.org Cc: gregkh@linuxfoundation.org, kvalo@codeaurora.org, Adham.Abozaeid@microchip.com, Venkateswara.Kaja@microchip.com, Nicolas.Ferre@microchip.com, Claudiu.Beznea@microchip.com Date: Fri, 12 Jul 2019 09:31:52 +0200 In-Reply-To: <1562896697-8002-6-git-send-email-ajay.kathat@microchip.com> References: <1562896697-8002-1-git-send-email-ajay.kathat@microchip.com> <1562896697-8002-6-git-send-email-ajay.kathat@microchip.com> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.28.5 (3.28.5-3.fc28) Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Sender: linux-wireless-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-wireless@vger.kernel.org On Fri, 2019-07-12 at 01:58 +0000, Ajay.Kathat@microchip.com wrote: > > + buf[0] = (u8)id; > + buf[1] = (u8)(id >> 8); > + buf[2] = 2; > + buf[3] = 0; > + buf[4] = (u8)val16; > + buf[5] = (u8)(val16 >> 8); There are helpers for that, put_le16_unaligned() or so? > + if (w->id == wid) { > + w->val = get_unaligned_le32(&info[4]); You use the opposite one here :-) > + /* > + * The valid types of response messages are > + * 'R' (Response), > + * 'I' (Information), and > + * 'N' (Network Information) > + */ > + > + switch (msg_type) { [...] > + case 'S': Hmm. :-) > + wl->cfg.str_vals = str_vals; > + /* store the string cfg parameters */ > + wl->cfg.s[i].id = WID_FIRMWARE_VERSION; > + wl->cfg.s[i].str = str_vals->firmware_version; > + i++; > + wl->cfg.s[i].id = WID_MAC_ADDR; > + wl->cfg.s[i].str = str_vals->mac_address; > + i++; > + wl->cfg.s[i].id = WID_ASSOC_RES_INFO; > + wl->cfg.s[i].str = str_vals->assoc_rsp; > + i++; > + wl->cfg.s[i].id = WID_NIL; > + wl->cfg.s[i].str = NULL; I really don't understand this style. Why not give it a proper struct and just say wl->cfg.assoc_rsp = str_vals->assoc_rsp; etc? johannes