Message ID | 20240625135216.47007-1-linyunsheng@huawei.com (mailing list archive) |
---|---|
Headers | show |
Series | First try to replace page_frag with page_frag_cache | expand |
On Tue, 25 Jun 2024 21:52:03 +0800 Yunsheng Lin wrote: > V9: > 1. Add check for test_alloc_len and change perm of module_param() > to 0 as Wang Wei' comment. > 2. Rebased on latest net-next. Please do not post a new version until you get feedback from Alex on the previous one. This series consumes all our CI resources, we can't get important patches tested :|
On Tue, Jun 25, 2024 at 4:27 PM Jakub Kicinski <kuba@kernel.org> wrote: > > On Tue, 25 Jun 2024 21:52:03 +0800 Yunsheng Lin wrote: > > V9: > > 1. Add check for test_alloc_len and change perm of module_param() > > to 0 as Wang Wei' comment. > > 2. Rebased on latest net-next. > > Please do not post a new version until you get feedback from Alex > on the previous one. This series consumes all our CI resources, > we can't get important patches tested :| Sorry, I didn't realize this patch set was waiting on feedback from me. I will try to get to it as time permits. Maybe a day or two as I have been swamped this week with various fbnic related items. Thanks, - Alex
On 2024/6/26 7:41, Alexander Duyck wrote: > On Tue, Jun 25, 2024 at 4:27 PM Jakub Kicinski <kuba@kernel.org> wrote: >> >> On Tue, 25 Jun 2024 21:52:03 +0800 Yunsheng Lin wrote: >>> V9: >>> 1. Add check for test_alloc_len and change perm of module_param() >>> to 0 as Wang Wei' comment. >>> 2. Rebased on latest net-next. >> >> Please do not post a new version until you get feedback from Alex >> on the previous one. This series consumes all our CI resources, >> we can't get important patches tested :| > > Sorry, I didn't realize this patch set was waiting on feedback from > me. I will try to get to it as time permits. Maybe a day or two as I > have been swamped this week with various fbnic related items. Ok, it would be good to have some feedback from you, thanks. > > Thanks, > > - Alex > . >
Silly nitpick, but maybe for the next version you change the Subject: to Tenth try to replace page_frag with page_frag.... :-) Andrew
On 2024/6/27 1:12, Andrew Lunn wrote: > Silly nitpick, but maybe for the next version you change the Subject: > to Tenth try to replace page_frag with page_frag.... :-) Yes, it is somewhat confusing for the 'First try' part. I guess I can change it to highlight the effort and commitment behind the trying:-) > > Andrew > . >
On Thu, 27 Jun 2024 19:16:22 +0800 Yunsheng Lin wrote: > On 2024/6/27 1:12, Andrew Lunn wrote: > > Silly nitpick, but maybe for the next version you change the Subject: > > to Tenth try to replace page_frag with page_frag.... :-) > > Yes, it is somewhat confusing for the 'First try' part. > I guess I can change it to highlight the effort and commitment behind > the trying:-) Sorry to ruin the slightly whimsical mood but if you do change it - please don't include the version at all. Some automation matches versions of patch sets together based on the title of the cover letter.
On 2024/6/28 3:58, Jakub Kicinski wrote: > On Thu, 27 Jun 2024 19:16:22 +0800 Yunsheng Lin wrote: >> On 2024/6/27 1:12, Andrew Lunn wrote: >>> Silly nitpick, but maybe for the next version you change the Subject: >>> to Tenth try to replace page_frag with page_frag.... :-) >> >> Yes, it is somewhat confusing for the 'First try' part. >> I guess I can change it to highlight the effort and commitment behind >> the trying:-) > > Sorry to ruin the slightly whimsical mood but if you do change it - > please don't include the version at all. Some automation matches > versions of patch sets together based on the title of the cover letter. Ok, perhaps it is more appropriate to change it to something like below: Replace page_frag with page_frag_cache for sk_page_frag() As this patchset is large enough that replacing is only done for sk_page_frag(), there are still other places using page_frag that can be replaced by page_frag_cache. > . >