From: Jakub Kicinski <kuba@kernel.org>
To: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
Cc: Willem de Bruijn <willemdebruijn.kernel@gmail.com>,
davem@davemloft.net, linux-bluetooth@vger.kernel.org,
netdev@vger.kernel.org, Pauli Virtanen <pav@iki.fi>
Subject: Re: pull request: bluetooth-next 2024-05-10
Date: Tue, 14 May 2024 07:34:02 -0700 [thread overview]
Message-ID: <20240514073402.72d2887c@kernel.org> (raw)
In-Reply-To: <CABBYNZ+f8L946_=6RyGvsN3bmu4EwJ2tTgxPg9YmNxckJTc_iw@mail.gmail.com>
On Mon, 13 May 2024 22:12:04 -0400 Luiz Augusto von Dentz wrote:
> > > It might be safer to only suppress the sk_error_report in
> > > sock_queue_err_skb. Or at least in bt_sock_poll to check the type of
> > > all outstanding errors and only suppress if all are timestamps.
> >
> > Or perhaps we could actually do that via poll/epoll directly? Not that
> > it would make it much simpler since the library tends to wrap the
> > usage of poll/epoll but POLLERR meaning both errors or errqueue events
> > is sort of the problem we are trying to figure out how to process them
> > separately.
>
> @Jakub Kicinski I'm fine removing these from the pull request, or if
> you want to do it yourself, in order not to miss the merge window,
> then we can discuss it better and even put you and Willem on CC to
> review the upcoming changes.
Sounds like the best way forward, thanks!
Could you drop them and resend the PR?
It's going to take me until noon pacific to write up the PR text
for all of net-next, to give you a sense of when our PR will come
out.
next prev parent reply other threads:[~2024-05-14 14:34 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-10 21:14 pull request: bluetooth-next 2024-05-10 Luiz Augusto von Dentz
2024-05-13 21:26 ` Jakub Kicinski
2024-05-13 22:09 ` Luiz Augusto von Dentz
2024-05-13 22:43 ` Jakub Kicinski
2024-05-14 1:32 ` Willem de Bruijn
2024-05-14 2:01 ` Luiz Augusto von Dentz
2024-05-14 2:09 ` Willem de Bruijn
2024-05-14 2:17 ` Luiz Augusto von Dentz
2024-05-14 2:25 ` Willem de Bruijn
2024-05-14 16:19 ` Pauli Virtanen
2024-05-14 18:40 ` Willem de Bruijn
2025-02-05 20:44 ` Luiz Augusto von Dentz
2025-02-06 17:13 ` Pauli Virtanen
2025-02-07 17:34 ` Luiz Augusto von Dentz
2024-05-14 2:12 ` Luiz Augusto von Dentz
2024-05-14 14:34 ` Jakub Kicinski [this message]
2024-05-14 14:44 ` Luiz Augusto von Dentz
2024-05-14 1:34 ` Luiz Augusto von Dentz
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=20240514073402.72d2887c@kernel.org \
--to=kuba@kernel.org \
--cc=davem@davemloft.net \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pav@iki.fi \
--cc=willemdebruijn.kernel@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).