From: Dan Carpenter <dan.carpenter@oracle.com>
To: Edmundo Carmona Antoranz <eantoranz@gmail.com>
Cc: kernel-janitors@vger.kernel.org
Subject: Re: [PATCH][next] loop: Fix missing max_active argument in alloc_workqueue call
Date: Fri, 19 Mar 2021 12:45:43 +0300 [thread overview]
Message-ID: <20210319094543.GG2087@kadam> (raw)
In-Reply-To: <CAOc6eta9oSxwPKma9ERP+BoXpW=PGaS8pxWiKQ3nj6BoYAu_Aw@mail.gmail.com>
On Thu, Mar 18, 2021 at 02:53:10PM -0600, Edmundo Carmona Antoranz wrote:
> On Thu, Mar 18, 2021 at 2:43 PM Jens Axboe <axboe@kernel.dk> wrote:
> >
>
> > If it's being redone, would be silly to have that error in there. Do
> > we have a tag that's appropriate for this? I often wonder when I'm
> > folding in a fix. Ala Fixes-by: or something like that.
> >
>
> Don't want to disturb the conversation that is going on there so I am
> only sending this question to janitors. What is the meaning of
> "folding" in this context?
Folding means you squash two patches together. The patch Colin was
fixing wasn't going to be merged for other reasons so we may as well
fix this as well when Dan resends.
regards,
dan carpenter
next prev parent reply other threads:[~2021-03-19 9:46 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-18 15:16 [PATCH][next] loop: Fix missing max_active argument in alloc_workqueue call Colin King
2021-03-18 19:18 ` Muhammad Usama Anjum
2021-03-18 20:12 ` Jens Axboe
2021-03-18 20:24 ` Colin Ian King
2021-03-18 20:42 ` Jens Axboe
2021-03-18 20:53 ` Edmundo Carmona Antoranz
2021-03-18 21:09 ` Julia Lawall
2021-03-18 21:11 ` Edmundo Carmona Antoranz
2021-03-19 9:45 ` Dan Carpenter [this message]
2021-03-19 9:47 ` Dan Carpenter
2021-03-19 10:03 ` Krzysztof Kozlowski
2021-03-19 13:02 ` Jens Axboe
2021-03-19 9:59 ` Krzysztof Kozlowski
2021-03-19 13:05 ` Jens Axboe
2021-03-19 15:51 ` Dan Schatzberg
2021-03-19 15:54 ` Dan Schatzberg
2021-03-19 15:56 ` Colin Ian King
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=20210319094543.GG2087@kadam \
--to=dan.carpenter@oracle.com \
--cc=eantoranz@gmail.com \
--cc=kernel-janitors@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.