From: Pete Zaitcev <zaitcev@redhat.com>
To: Martin Schwidefsky <schwidefsky@de.ibm.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] s390 (5/7): kmalloc arguments.
Date: Fri, 7 Mar 2003 15:08:01 -0500 [thread overview]
Message-ID: <200303072008.h27K81j19556@devserv.devel.redhat.com> (raw)
In-Reply-To: <mailman.1047042481.25045.linux-kernel2news@redhat.com>
> Add missing GFP_KERNEL to kmallocs with GFP_DMA.
> - sch = kmalloc (sizeof (*sch), GFP_DMA);
> + sch = kmalloc (sizeof (*sch), GFP_KERNEL | GFP_DMA);
> if (sch == NULL)
> return -ENOMEM;
Would you mind explaining why you are doing this?
What does GFP_DMA do on s390 and s390x?
-- Pete
next parent reply other threads:[~2003-03-07 19:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.1047042481.25045.linux-kernel2news@redhat.com>
2003-03-07 20:08 ` Pete Zaitcev [this message]
2003-03-07 21:13 [PATCH] s390 (5/7): kmalloc arguments Ulrich Weigand
-- strict thread matches above, loose matches on Subject: below --
2003-03-07 12:38 Martin Schwidefsky
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=200303072008.h27K81j19556@devserv.devel.redhat.com \
--to=zaitcev@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=schwidefsky@de.ibm.com \
/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).