From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Ricardo Ribalda <ribalda@chromium.org>
Cc: Zubin Mithra <zsm@chromium.org>,
Chunfeng Yun <chunfeng.yun@mediatek.com>,
Mathias Nyman <mathias.nyman@intel.com>,
Matthias Brugger <matthias.bgg@gmail.com>,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com>,
linux-usb@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] usb: xhci-mtk: set the dma max_seg_size
Date: Thu, 29 Jun 2023 10:40:09 +0200 [thread overview]
Message-ID: <2023062942-thumb-giddily-f0e0@gregkh> (raw)
In-Reply-To: <CANiDSCu3WOqK9wdLDXmW+zbckq15gmxKjtFA4Aghv6uoidO_3Q@mail.gmail.com>
On Thu, Jun 29, 2023 at 09:13:23AM +0200, Ricardo Ribalda wrote:
> Hi Zubin
>
> On Wed, 28 Jun 2023 at 23:57, Zubin Mithra <zsm@chromium.org> wrote:
> >
> > On Wed, Jun 28, 2023 at 11:04:20PM +0200, Ricardo Ribalda wrote:
> > > On Wed, 28 Jun 2023 at 23:00, Ricardo Ribalda <ribalda@chromium.org> wrote:
> > > >
> > > > Allow devices to have dma operations beyond 64K, and avoid warnings such
> > > > as:
> > > >
> > > > DMA-API: xhci-mtk 11200000.usb: mapping sg segment longer than device claims to support [len=98304] [max=65536]
> > > >
> > > > Signed-off-by: Ricardo Ribalda <ribalda@chromium.org>
> > > Reported-by: Zubin Mithra <zsm@chromium.org>
> >
> > Should this be cc'd to stable@ as well?
>
> Not sure, in most of the cases this is "just" a warning fix. Let the
> maintainer decide:
Warnings can cause reboots as the majority of the linux systems in the
world run panic-on-warn, so yes, it should be backported.
thanks,
greg k-h
next prev parent reply other threads:[~2023-06-29 8:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-28 21:00 [PATCH] usb: xhci-mtk: set the dma max_seg_size Ricardo Ribalda
2023-06-28 21:04 ` Ricardo Ribalda
2023-06-28 21:57 ` Zubin Mithra
2023-06-29 7:13 ` Ricardo Ribalda
2023-06-29 8:40 ` Greg Kroah-Hartman [this message]
2023-06-29 11:40 ` Robin Murphy
2023-06-29 18:11 ` Robin Murphy
2023-06-29 18:29 ` Ricardo Ribalda
2023-06-29 19:19 ` Robin Murphy
2023-06-30 11:25 ` Mathias Nyman
2023-07-04 5:57 ` Chunfeng Yun (云春峰)
2023-07-04 6:07 ` Chunfeng Yun (云春峰)
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=2023062942-thumb-giddily-f0e0@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=angelogioacchino.delregno@collabora.com \
--cc=chunfeng.yun@mediatek.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-usb@vger.kernel.org \
--cc=mathias.nyman@intel.com \
--cc=matthias.bgg@gmail.com \
--cc=ribalda@chromium.org \
--cc=zsm@chromium.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox