LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Stefan Metzmacher <metze@samba.org>
To: Jens Axboe <axboe@kernel.dk>, Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: Signed-off-by missing for commit in the block tree
Date: Fri, 19 Mar 2021 14:10:19 +0100 [thread overview]
Message-ID: <6cf57986-45c6-fb00-eb19-c7f4aeac82a5@samba.org> (raw)
In-Reply-To: <6fc61af0-e113-15d3-dd71-a0415b0f546f@kernel.dk>
Am 19.03.21 um 14:08 schrieb Jens Axboe:
> On 3/19/21 2:02 AM, Stefan Metzmacher wrote:
>>
>> Am 19.03.21 um 00:25 schrieb Jens Axboe:
>>> On 3/18/21 5:16 PM, Stephen Rothwell wrote:
>>>> Hi all,
>>>>
>>>> Commit
>>>>
>>>> c2c6c067c050 ("io_uring: remove structures from include/linux/io_uring.h")
>>>>
>>>> is missing a Signed-off-by from its author.
>>>
>>> Stefan, let me know if you're OK with me adding that, not sure how I missed
>>> that.
>>
>> Yes, sure :-)
>> I guess you removed it while adding 'Link:'
>
> That was b4, I don't add those manually. But maybe it stripped those too,
> annoying...
>
>> You may want to remove cc: stable from 3aab52c9a708f7183460d368700181ef0c2a09e6
>> ("io_uring: imply MSG_NOSIGNAL for send[msg]()/recv[msg]() calls")
>> for now.
>>
>> I'll want to do some more test with it on 5.12,
>> I guess we'd then have to backport it to stable as part of the
>> io_thread worker backport. I'll post some more details later
>> to the io-uring list.
>
> Sure, let's do that. I also dropped the short link sever as well for now.
> I do like it on principle, but it does have a risk of breaking valid
> use cases.
Thanks, I'll resubmit that with the MSG_WAITALL logic.
metze
next prev parent reply other threads:[~2021-03-19 13:11 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-18 23:16 Stephen Rothwell
2021-03-18 23:25 ` Jens Axboe
2021-03-19 8:02 ` Stefan Metzmacher
2021-03-19 13:08 ` Jens Axboe
2021-03-19 13:10 ` Stefan Metzmacher [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-01-22 21:08 Stephen Rothwell
2023-01-22 21:30 ` Jens Axboe
2023-01-22 21:34 ` Stephen Rothwell
2023-01-22 21:37 ` Jens Axboe
2022-07-20 13:16 Stephen Rothwell
2022-07-20 13:21 ` Christoph Hellwig
2022-07-20 15:58 ` Jens Axboe
2022-03-29 21:11 Stephen Rothwell
2022-03-30 5:00 ` Christoph Hellwig
2021-08-10 21:58 Stephen Rothwell
2021-06-08 22:31 Stephen Rothwell
2021-04-11 22:34 Stephen Rothwell
2021-04-12 2:14 ` Jens Axboe
2021-04-12 2:26 ` Sowjanya Komatineni
2021-04-12 2:36 ` Jens Axboe
2021-03-04 23:54 Stephen Rothwell
2021-01-25 9:43 Stephen Rothwell
2021-01-25 15:18 ` Jens Axboe
2020-12-02 20:52 Stephen Rothwell
2020-06-26 23:08 Stephen Rothwell
2020-04-08 21:59 Stephen Rothwell
2019-05-22 21:50 Stephen Rothwell
2019-05-22 23:26 ` Jens Axboe
2018-12-16 6:26 Stephen Rothwell
2018-12-16 10:18 ` Christoph Hellwig
2018-12-16 15:33 ` Jens Axboe
2018-08-05 21:51 Stephen Rothwell
2018-08-06 1:16 ` Jens Axboe
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=6cf57986-45c6-fb00-eb19-c7f4aeac82a5@samba.org \
--to=metze@samba.org \
--cc=axboe@kernel.dk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--subject='Re: linux-next: Signed-off-by missing for commit in the block tree' \
/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
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).