From: Yves-Alexis Perez <corsac@corsac.net>
To: Hans de Goede <hdegoede@redhat.com>, Gerd Hoffmann <kraxel@redhat.com>
Cc: linux-usb@vger.kernel.org, linux-scsi@vger.kernel.org
Subject: Re: Page allocation failure (order 7) in UAS code
Date: Fri, 04 Mar 2016 14:28:11 +0100 [thread overview]
Message-ID: <1457098091.23913.6.camel@corsac.net> (raw)
In-Reply-To: <56D936A8.208@redhat.com>
On ven., 2016-03-04 at 08:18 +0100, Hans de Goede wrote:
> Thanks for testing, there shouldn't be any side-effects, I'll turn this into
> a proper patch, add a:
>
> Reported-and-tested-by: Yves-Alexis Perez <corsac@corsac.net>
>
> line to the comit msg and submit this upstream.
>
>
Thanks,
I guess it can also be CC: stable@ since it started in 4.4.
Regards,
--
Yves-Alexis
prev parent reply other threads:[~2016-03-04 13:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-01 9:42 Page allocation failure (order 7) in UAS code Yves-Alexis Perez
2016-03-01 10:49 ` Hans de Goede
2016-03-01 11:20 ` Yves-Alexis Perez
[not found] ` <56D573CF.1000600-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2016-03-04 7:13 ` Yves-Alexis Perez
2016-03-04 7:18 ` Hans de Goede
2016-03-04 13:28 ` Yves-Alexis Perez [this message]
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=1457098091.23913.6.camel@corsac.net \
--to=corsac@corsac.net \
--cc=hdegoede@redhat.com \
--cc=kraxel@redhat.com \
--cc=linux-scsi@vger.kernel.org \
--cc=linux-usb@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox