From: Kalle Valo <kvalo-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
To: Sid Hayn <sidhayn-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: sgruszka-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org,
Lorenzo Bianconi
<lorenzo.bianconi-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>,
Felix Fietkau <nbd-Vt+b4OUoWG0@public.gmane.org>,
linux-wireless
<linux-wireless-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
linux-mediatek-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org
Subject: Re: [PATCH] mt76x0: run vco calibration for each channel configuration
Date: Wed, 19 Sep 2018 15:03:52 +0300 [thread overview]
Message-ID: <87worh1yon.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <CAM0KTbAPHPK04SntA9UL0rGaaNjTy=E2hRoO7xiRkbMcq9b7Sw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org> (Sid Hayn's message of "Tue, 18 Sep 2018 10:26:09 -0400")
Sid Hayn <sidhayn-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> writes:
> mt76x0 isn't in 4.18 at all, it's being added in 4.19 isn't it? I'm
> not sure you can call it a regression, but adding a new driver with a
> known bug that breaks an entire use case (monitor mode) seems silly
> when a small and tested fix is available. Pretty please.
Unfortunately it's not that simple as you think. And do take into
account that the maintainers need to deal with a lot of patches and
email so keeping things simple is important.
And please do not top post:
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches#do_not_top_post_and_edit_your_quotes
--
Kalle Valo
WARNING: multiple messages have this Message-ID (diff)
From: Kalle Valo <kvalo@codeaurora.org>
To: Sid Hayn <sidhayn@gmail.com>
Cc: sgruszka@redhat.com,
Lorenzo Bianconi <lorenzo.bianconi@redhat.com>,
Felix Fietkau <nbd@nbd.name>,
linux-wireless <linux-wireless@vger.kernel.org>,
linux-mediatek@lists.infradead.org
Subject: Re: [PATCH] mt76x0: run vco calibration for each channel configuration
Date: Wed, 19 Sep 2018 15:03:52 +0300 [thread overview]
Message-ID: <87worh1yon.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <CAM0KTbAPHPK04SntA9UL0rGaaNjTy=E2hRoO7xiRkbMcq9b7Sw@mail.gmail.com> (Sid Hayn's message of "Tue, 18 Sep 2018 10:26:09 -0400")
Sid Hayn <sidhayn@gmail.com> writes:
> mt76x0 isn't in 4.18 at all, it's being added in 4.19 isn't it? I'm
> not sure you can call it a regression, but adding a new driver with a
> known bug that breaks an entire use case (monitor mode) seems silly
> when a small and tested fix is available. Pretty please.
Unfortunately it's not that simple as you think. And do take into
account that the maintainers need to deal with a lot of patches and
email so keeping things simple is important.
And please do not top post:
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches#do_not_top_post_and_edit_your_quotes
--
Kalle Valo
next prev parent reply other threads:[~2018-09-19 12:03 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-07 21:13 [PATCH] mt76x0: run vco calibration for each channel configuration Lorenzo Bianconi
2018-09-07 21:13 ` Lorenzo Bianconi
[not found] ` <20180907211312.17918-1-lorenzo.bianconi-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2018-09-18 11:43 ` Stanislaw Gruszka
2018-09-18 11:43 ` Stanislaw Gruszka
[not found] ` <20180918114356.GB15285-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2018-09-18 12:02 ` Stanislaw Gruszka
2018-09-18 12:02 ` Stanislaw Gruszka
[not found] ` <20180918120234.GD15285-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2018-09-18 12:40 ` Kalle Valo
2018-09-18 12:40 ` Kalle Valo
[not found] ` <871s9r2d3g.fsf-HodKDYzPHsUD5k0oWYwrnHL1okKdlPRT@public.gmane.org>
2018-09-18 14:26 ` Sid Hayn
2018-09-18 14:26 ` Sid Hayn
[not found] ` <CAM0KTbAPHPK04SntA9UL0rGaaNjTy=E2hRoO7xiRkbMcq9b7Sw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2018-09-19 11:24 ` Stanislaw Gruszka
2018-09-19 11:24 ` Stanislaw Gruszka
2018-09-19 12:03 ` Kalle Valo [this message]
2018-09-19 12:03 ` Kalle Valo
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=87worh1yon.fsf@kamboji.qca.qualcomm.com \
--to=kvalo-sgv2jx0feol9jmxxk+q4oq@public.gmane.org \
--cc=linux-mediatek-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=linux-wireless-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=lorenzo.bianconi-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=nbd-Vt+b4OUoWG0@public.gmane.org \
--cc=sgruszka-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=sidhayn-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.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.