public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Andrey Zhizhikin <andrey.zhizhikin@leica-geosystems.com>
Cc: davem@davemloft.net, kuba@kernel.org, jussi.kivilinna@mbnet.fi,
	dbrownell@users.sourceforge.net, linville@tuxdriver.com,
	linux-usb@vger.kernel.org, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] rndis_host: set proper input size for OID_GEN_PHYSICAL_MEDIUM request
Date: Tue, 12 Jan 2021 02:00:08 +0000	[thread overview]
Message-ID: <161041680859.7943.15802296130984944165.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210108095839.3335-1-andrey.zhizhikin@leica-geosystems.com>

Hello:

This patch was applied to netdev/net.git (refs/heads/master):

On Fri,  8 Jan 2021 09:58:39 +0000 you wrote:
> MSFT ActiveSync implementation requires that the size of the response for
> incoming query is to be provided in the request input length. Failure to
> set the input size proper results in failed request transfer, where the
> ActiveSync counterpart reports the NDIS_STATUS_INVALID_LENGTH (0xC0010014L)
> error.
> 
> Set the input size for OID_GEN_PHYSICAL_MEDIUM query to the expected size
> of the response in order for the ActiveSync to properly respond to the
> request.
> 
> [...]

Here is the summary with links:
  - rndis_host: set proper input size for OID_GEN_PHYSICAL_MEDIUM request
    https://git.kernel.org/netdev/net/c/e56b3d94d939

You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      reply	other threads:[~2021-01-12  2:01 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-08  9:58 [PATCH] rndis_host: set proper input size for OID_GEN_PHYSICAL_MEDIUM request Andrey Zhizhikin
2021-01-12  2:00 ` patchwork-bot+netdevbpf [this message]

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=161041680859.7943.15802296130984944165.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=andrey.zhizhikin@leica-geosystems.com \
    --cc=davem@davemloft.net \
    --cc=dbrownell@users.sourceforge.net \
    --cc=jussi.kivilinna@mbnet.fi \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=netdev@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