All of lore.kernel.org
 help / color / mirror / Atom feed
From: vnaralas@codeaurora.org
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless@vger.kernel.org, linux-wireless-owner@vger.kernel.org
Subject: Re: [PATCH] cfg80211: Add cumulative channel survey dump support.
Date: Thu, 31 May 2018 14:36:59 +0530	[thread overview]
Message-ID: <ebf1c95acb34649b3d2a5435142dc06a@codeaurora.org> (raw)
In-Reply-To: <1527069282.3759.16.camel@sipsolutions.net>

On 2018-05-23 15:24, Johannes Berg wrote:
> On Tue, 2018-05-22 at 14:45 +0530, Venkateswara Naralasetty wrote:
>> This patch provides support to send accumulated survey data to
>> user if low level drivers provides non-accumulated survey data.
> 
> I think the commit log should say what you need this for?
> 
> It's simultaneously a new flag, and a lot of code, but it's not clear
> what the point is?
> 
> johannes

I will sent next version of patch with updated commit log.

Providing you the earlier discussion of this patch to give quick 
overview about this patch.
https://patchwork.kernel.org/patch/9701459/


Thanks,
Venkatesh.

  reply	other threads:[~2018-05-31  9:07 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-22  9:15 [PATCH] cfg80211: Add cumulative channel survey dump support Venkateswara Naralasetty
2018-05-23  9:54 ` Johannes Berg
2018-05-31  9:06   ` vnaralas [this message]
2018-05-31 15:52     ` Ben Greear
2018-06-18 20:46       ` Johannes Berg
2018-06-18 20:57         ` Ben Greear
2018-06-18 20:45     ` Johannes Berg
2019-09-17 17:27     ` Sven Eckelmann
2019-09-17 17:27       ` Sven Eckelmann
2019-09-17 17:44       ` Ben Greear
2019-09-17 17:44         ` Ben Greear
2019-09-18  8:46       ` Sven Eckelmann
2019-09-18  8:46         ` Sven Eckelmann
2019-09-18 12:58         ` Ben Greear
2019-09-18 12:58           ` Ben Greear
2019-09-18 13:07           ` Sven Eckelmann
2019-09-18 13:07             ` Sven Eckelmann
2019-09-18 13:13             ` Sven Eckelmann
2019-09-18 13:13               ` Sven Eckelmann

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=ebf1c95acb34649b3d2a5435142dc06a@codeaurora.org \
    --to=vnaralas@codeaurora.org \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless-owner@vger.kernel.org \
    --cc=linux-wireless@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 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.