From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Jia-Ju Bai <baijiaju1990@gmail.com>
Cc: Kai.Makisara@kolumbus.fi, jejb@linux.vnet.ibm.com,
martin.petersen@oracle.com, linux-scsi@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] scsi: st: Replace GFP_ATOMIC with GFP_KERNEL in st_probe
Date: Fri, 20 Apr 2018 18:38:06 -0400 [thread overview]
Message-ID: <yq1y3hhh5bl.fsf@oracle.com> (raw)
In-Reply-To: <1523363879-31242-1-git-send-email-baijiaju1990@gmail.com> (Jia-Ju Bai's message of "Tue, 10 Apr 2018 20:37:59 +0800")
Jia-Ju,
> st_probe() is never called in atomic context.
Applied patches 1 and 2 to 4.18/scsi-queue. Thanks!
--
Martin K. Petersen Oracle Linux Engineering
prev parent reply other threads:[~2018-04-20 22:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-10 12:37 [PATCH 1/2] scsi: st: Replace GFP_ATOMIC with GFP_KERNEL in st_probe Jia-Ju Bai
2018-04-20 22:38 ` Martin K. Petersen [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=yq1y3hhh5bl.fsf@oracle.com \
--to=martin.petersen@oracle.com \
--cc=Kai.Makisara@kolumbus.fi \
--cc=baijiaju1990@gmail.com \
--cc=jejb@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@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;
as well as URLs for NNTP newsgroup(s).