From: Chris Lew <clew@codeaurora.org>
To: Bjorn Andersson <bjorn.andersson@linaro.org>,
"David S. Miller" <davem@davemloft.net>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH 1/7] net: qrtr: Invoke sk_error_report() after setting sk_err
Date: Thu, 21 Sep 2017 11:27:26 -0700 [thread overview]
Message-ID: <c7b2cee7-06d2-b3db-07dc-cdf6c850c12b@codeaurora.org> (raw)
In-Reply-To: <20170907060329.32402-2-bjorn.andersson@linaro.org>
On 9/6/2017 11:03 PM, Bjorn Andersson wrote:
> Rather than manually waking up any context sleeping on the sock to
> signal an error we should call sk_error_report(). This has the added
> benefit that in-kernel consumers can override this notificatino with
> its own callback.
>
Typo with notification.
Thanks,
Chris
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
next prev parent reply other threads:[~2017-09-21 18:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-07 6:03 [PATCH 0/7] net: qrtr: Fixes and support receiving version 2 packets Bjorn Andersson
2017-09-07 6:03 ` [PATCH 1/7] net: qrtr: Invoke sk_error_report() after setting sk_err Bjorn Andersson
2017-09-21 18:27 ` Chris Lew [this message]
2017-09-07 6:03 ` [PATCH 2/7] net: qrtr: Move constants to header file Bjorn Andersson
2017-09-07 6:03 ` [PATCH 3/7] net: qrtr: Add control packet definition to uapi Bjorn Andersson
2017-09-07 6:03 ` [PATCH 4/7] net: qrtr: Pass source and destination to enqueue functions Bjorn Andersson
2017-09-07 6:03 ` [PATCH 5/7] net: qrtr: Clean up control packet handling Bjorn Andersson
2017-09-07 6:03 ` [PATCH 6/7] net: qrtr: Use sk_buff->cb in receive path Bjorn Andersson
2017-09-07 6:03 ` [PATCH 7/7] net: qrtr: Support decoding incoming v2 packets Bjorn Andersson
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=c7b2cee7-06d2-b3db-07dc-cdf6c850c12b@codeaurora.org \
--to=clew@codeaurora.org \
--cc=bjorn.andersson@linaro.org \
--cc=davem@davemloft.net \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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
Powered by JetHome