| Message ID | 20170813170219.GG18698@decadent.org.uk (mailing list archive) |
|---|---|
| State | New, archived |
| Headers | show |
On Sun, Aug 13, 2017 at 06:02:19PM +0100, Ben Hutchings wrote: > The block core requests modules with the "-iosched" name suffix, but > bfq no longer has that suffix. Add an alias. > > Fixes: ea25da48086d ("block, bfq: split bfq-iosched.c into multiple ...") > Signed-off-by: Ben Hutchings <ben@decadent.org.uk> > --- > block/bfq-iosched.c | 1 + > 1 file changed, 1 insertion(+) > > diff --git a/block/bfq-iosched.c b/block/bfq-iosched.c > index 436b6ca6b175..3a01563bd564 100644 > --- a/block/bfq-iosched.c > +++ b/block/bfq-iosched.c > @@ -4998,6 +4998,7 @@ static struct elevator_type iosched_bfq_mq = { > .elevator_name = "bfq", > .elevator_owner = THIS_MODULE, > }; > +MODULE_ALIAS("bfq-iosched"); > > static int __init bfq_init(void) > { > Reviewed-by: Ming Lei <ming.lei@redhat.com>
On Sun, Aug 13 2017, Ben Hutchings wrote: > The block core requests modules with the "-iosched" name suffix, but > bfq no longer has that suffix. Add an alias. I'd apply these two, but both patches are mangled when saved. It's turning == into =3D and so forth. Care to check your settings and resend?
On Tue, 2017-08-29 at 08:31 -0600, Jens Axboe wrote: > On Sun, Aug 13 2017, Ben Hutchings wrote: > > The block core requests modules with the "-iosched" name suffix, but > > bfq no longer has that suffix. Add an alias. > > I'd apply these two, but both patches are mangled when saved. It's > turning == into =3D and so forth. > > Care to check your settings and resend? Just tried saving and applying with 'git am' successfully. I think the problem is at your end. Ben.
On 08/29/2017 09:28 AM, Ben Hutchings wrote: > On Tue, 2017-08-29 at 08:31 -0600, Jens Axboe wrote: >> On Sun, Aug 13 2017, Ben Hutchings wrote: >>> The block core requests modules with the "-iosched" name suffix, but >>> bfq no longer has that suffix. Add an alias. >> >> I'd apply these two, but both patches are mangled when saved. It's >> turning == into =3D and so forth. >> >> Care to check your settings and resend? > > Just tried saving and applying with 'git am' successfully. I think the > problem is at your end. Then yours is the only one, I apply patches people send me all day long. Was the case both in tbird and mutt, both of them showed the diffs as mangled, and they showed up mangled when saved.
On 08/29/2017 09:48 AM, Jens Axboe wrote: > On 08/29/2017 09:28 AM, Ben Hutchings wrote: >> On Tue, 2017-08-29 at 08:31 -0600, Jens Axboe wrote: >>> On Sun, Aug 13 2017, Ben Hutchings wrote: >>>> The block core requests modules with the "-iosched" name suffix, but >>>> bfq no longer has that suffix. Add an alias. >>> >>> I'd apply these two, but both patches are mangled when saved. It's >>> turning == into =3D and so forth. >>> >>> Care to check your settings and resend? >> >> Just tried saving and applying with 'git am' successfully. I think the >> problem is at your end. > > Then yours is the only one, I apply patches people send me all day long. > Was the case both in tbird and mutt, both of them showed the diffs > as mangled, and they showed up mangled when saved. Here's your email in the archive: https://marc.info/?l=linux-block&m=150264374920778&q=raw Note this part: Content-Transfer-Encoding: quoted-printable Problem is definitely at your end.
On Tue, 2017-08-29 at 09:53 -0600, Jens Axboe wrote: > On 08/29/2017 09:48 AM, Jens Axboe wrote: > > On 08/29/2017 09:28 AM, Ben Hutchings wrote: > > > On Tue, 2017-08-29 at 08:31 -0600, Jens Axboe wrote: > > > > On Sun, Aug 13 2017, Ben Hutchings wrote: > > > > > The block core requests modules with the "-iosched" name > > > > > suffix, but > > > > > bfq no longer has that suffix. Add an alias. > > > > > > > > I'd apply these two, but both patches are mangled when saved. > > > > It's > > > > turning == into =3D and so forth. > > > > > > > > Care to check your settings and resend? > > > > > > Just tried saving and applying with 'git am' successfully. I > > > think the > > > problem is at your end. > > > > Then yours is the only one, I apply patches people send me all day > > long. > > Was the case both in tbird and mutt, both of them showed the diffs > > as mangled, and they showed up mangled when saved. > > Here's your email in the archive: > > https://marc.info/?l=linux-block&m=150264374920778&q=raw > > Note this part: > > Content-Transfer-Encoding: quoted-printable What about it? This is used for every mail with a non-ASCII name in it, for example. 'git am' understands it. > Problem is definitely at your end. Or perhaps in the middle? Anyway, here are the patches again as an mbox. Ben.
On 08/29/2017 10:34 AM, Ben Hutchings wrote: > On Tue, 2017-08-29 at 09:53 -0600, Jens Axboe wrote: >> On 08/29/2017 09:48 AM, Jens Axboe wrote: >>> On 08/29/2017 09:28 AM, Ben Hutchings wrote: >>>> On Tue, 2017-08-29 at 08:31 -0600, Jens Axboe wrote: >>>>> On Sun, Aug 13 2017, Ben Hutchings wrote: >>>>>> The block core requests modules with the "-iosched" name >>>>>> suffix, but >>>>>> bfq no longer has that suffix. Add an alias. >>>>> >>>>> I'd apply these two, but both patches are mangled when saved. >>>>> It's >>>>> turning == into =3D and so forth. >>>>> >>>>> Care to check your settings and resend? >>>> >>>> Just tried saving and applying with 'git am' successfully. I >>>> think the >>>> problem is at your end. >>> >>> Then yours is the only one, I apply patches people send me all day >>> long. >>> Was the case both in tbird and mutt, both of them showed the diffs >>> as mangled, and they showed up mangled when saved. >> >> Here's your email in the archive: >> >> https://marc.info/?l=linux-block&m=150264374920778&q=raw >> >> Note this part: >> >> Content-Transfer-Encoding: quoted-printable > > What about it? This is used for every mail with a non-ASCII name in > it, for example. 'git am' understands it. What about it? It screws up the patch. Maybe git am understands it, but it's hard/impossible to read manually. I'm not going to apply anything that I can't personally read/review easily. Fix your setup, if you are going to be sending patches. >> Problem is definitely at your end. > > Or perhaps in the middle? Anyway, here are the patches again as an > mbox. Feel free to browse other patches on the list, I don't see any that are quoted-printable. And I'd know, since I generally end up applying (or at least reviewing) most of them.
On Tue, 2017-08-29 at 10:46 -0600, Jens Axboe wrote: > On 08/29/2017 10:34 AM, Ben Hutchings wrote: > > On Tue, 2017-08-29 at 09:53 -0600, Jens Axboe wrote: > > > On 08/29/2017 09:48 AM, Jens Axboe wrote: > > > > On 08/29/2017 09:28 AM, Ben Hutchings wrote: > > > > > On Tue, 2017-08-29 at 08:31 -0600, Jens Axboe wrote: > > > > > > On Sun, Aug 13 2017, Ben Hutchings wrote: > > > > > > > The block core requests modules with the "-iosched" name > > > > > > > suffix, but > > > > > > > bfq no longer has that suffix. Add an alias. > > > > > > > > > > > > I'd apply these two, but both patches are mangled when saved. > > > > > > It's > > > > > > turning == into =3D and so forth. > > > > > > > > > > > > Care to check your settings and resend? > > > > > > > > > > Just tried saving and applying with 'git am' successfully. I > > > > > think the > > > > > problem is at your end. > > > > > > > > Then yours is the only one, I apply patches people send me all day > > > > long. > > > > Was the case both in tbird and mutt, both of them showed the diffs > > > > as mangled, and they showed up mangled when saved. > > > > > > Here's your email in the archive: > > > > > > https://marc.info/?l=linux-block&m=150264374920778&q=raw > > > > > > Note this part: > > > > > > Content-Transfer-Encoding: quoted-printable > > > > What about it? This is used for every mail with a non-ASCII name in > > it, for example. 'git am' understands it. > > What about it? It screws up the patch. Maybe git am understands it, but > it's hard/impossible to read manually. Where, other than the 'raw' link above, are you seeing the patch with q-p encoding not decoded? > I'm not going to apply anything > that I can't personally read/review easily. Fix your setup, if you are > going to be sending patches. So you won't accept patches from anyone with a non-ASCII name? Ben. > > > Problem is definitely at your end. > > > > Or perhaps in the middle? Anyway, here are the patches again as an > > mbox. > > Feel free to browse other patches on the list, I don't see any that > are quoted-printable. And I'd know, since I generally end up applying > (or at least reviewing) most of them. >
On 08/29/2017 01:49 PM, Ben Hutchings wrote: > On Tue, 2017-08-29 at 10:46 -0600, Jens Axboe wrote: >> On 08/29/2017 10:34 AM, Ben Hutchings wrote: >>> On Tue, 2017-08-29 at 09:53 -0600, Jens Axboe wrote: >>>> On 08/29/2017 09:48 AM, Jens Axboe wrote: >>>>> On 08/29/2017 09:28 AM, Ben Hutchings wrote: >>>>>> On Tue, 2017-08-29 at 08:31 -0600, Jens Axboe wrote: >>>>>>> On Sun, Aug 13 2017, Ben Hutchings wrote: >>>>>>>> The block core requests modules with the "-iosched" name >>>>>>>> suffix, but >>>>>>>> bfq no longer has that suffix. Add an alias. >>>>>>> >>>>>>> I'd apply these two, but both patches are mangled when saved. >>>>>>> It's >>>>>>> turning == into =3D and so forth. >>>>>>> >>>>>>> Care to check your settings and resend? >>>>>> >>>>>> Just tried saving and applying with 'git am' successfully. I >>>>>> think the >>>>>> problem is at your end. >>>>> >>>>> Then yours is the only one, I apply patches people send me all day >>>>> long. >>>>> Was the case both in tbird and mutt, both of them showed the diffs >>>>> as mangled, and they showed up mangled when saved. >>>> >>>> Here's your email in the archive: >>>> >>>> https://marc.info/?l=linux-block&m=150264374920778&q=raw >>>> >>>> Note this part: >>>> >>>> Content-Transfer-Encoding: quoted-printable >>> >>> What about it? This is used for every mail with a non-ASCII name in >>> it, for example. 'git am' understands it. >> >> What about it? It screws up the patch. Maybe git am understands it, but >> it's hard/impossible to read manually. > > Where, other than the 'raw' link above, are you seeing the patch with > q-p encoding not decoded? When I save it and view it. >> I'm not going to apply anything >> that I can't personally read/review easily. Fix your setup, if you are >> going to be sending patches. > > So you won't accept patches from anyone with a non-ASCII name? You're being ridiculous.
On Tue, 2017-08-29 at 13:57 -0600, Jens Axboe wrote: > On 08/29/2017 01:49 PM, Ben Hutchings wrote: > > On Tue, 2017-08-29 at 10:46 -0600, Jens Axboe wrote: > > > On 08/29/2017 10:34 AM, Ben Hutchings wrote: > > > > On Tue, 2017-08-29 at 09:53 -0600, Jens Axboe wrote: > > > > > On 08/29/2017 09:48 AM, Jens Axboe wrote: > > > > > > On 08/29/2017 09:28 AM, Ben Hutchings wrote: > > > > > > > On Tue, 2017-08-29 at 08:31 -0600, Jens Axboe wrote: > > > > > > > > On Sun, Aug 13 2017, Ben Hutchings wrote: > > > > > > > > > The block core requests modules with the "-iosched" name > > > > > > > > > suffix, but > > > > > > > > > bfq no longer has that suffix. Add an alias. > > > > > > > > > > > > > > > > I'd apply these two, but both patches are mangled when saved. > > > > > > > > It's > > > > > > > > turning == into =3D and so forth. > > > > > > > > > > > > > > > > Care to check your settings and resend? > > > > > > > > > > > > > > Just tried saving and applying with 'git am' successfully. I > > > > > > > think the > > > > > > > problem is at your end. > > > > > > > > > > > > Then yours is the only one, I apply patches people send me all day > > > > > > long. > > > > > > Was the case both in tbird and mutt, both of them showed the diffs > > > > > > as mangled, and they showed up mangled when saved. > > > > > > > > > > Here's your email in the archive: > > > > > > > > > > https://marc.info/?l=linux-block&m=150264374920778&q=raw > > > > > > > > > > Note this part: > > > > > > > > > > Content-Transfer-Encoding: quoted-printable > > > > > > > > What about it? This is used for every mail with a non-ASCII name in > > > > it, for example. 'git am' understands it. > > > > > > What about it? It screws up the patch. Maybe git am understands it, but > > > it's hard/impossible to read manually. > > > > Where, other than the 'raw' link above, are you seeing the patch with > > q-p encoding not decoded? > > When I save it and view it. I don't understand why you wouldn't do that in your mailer. You're going to need to switch back to the mailer when you reply, after all. But if you want to display a quoted-printable file in a terminal, you can use 'qprint -d' to do that. > > > I'm not going to apply anything > > > that I can't personally read/review easily. Fix your setup, if you are > > > going to be sending patches. > > > > So you won't accept patches from anyone with a non-ASCII name? > > You're being ridiculous. Am I? It seems like they would trigger the same problem in your current workflow. Ben.
diff --git a/block/bfq-iosched.c b/block/bfq-iosched.c index 436b6ca6b175..3a01563bd564 100644 --- a/block/bfq-iosched.c +++ b/block/bfq-iosched.c @@ -4998,6 +4998,7 @@ static struct elevator_type iosched_bfq_mq = { .elevator_name = "bfq", .elevator_owner = THIS_MODULE, }; +MODULE_ALIAS("bfq-iosched"); static int __init bfq_init(void) {
The block core requests modules with the "-iosched" name suffix, but bfq no longer has that suffix. Add an alias. Fixes: ea25da48086d ("block, bfq: split bfq-iosched.c into multiple ...") Signed-off-by: Ben Hutchings <ben@decadent.org.uk> --- block/bfq-iosched.c | 1 + 1 file changed, 1 insertion(+)