From: Colin Ian King <colin.king@canonical.com>
To: Ursula Braun <ubraun@linux.ibm.com>, linux-s390@vger.kernel.org
Cc: Julian Wiedmann <jwi@linux.ibm.com>,
Vasily Gorbik <gor@linux.ibm.com>,
Christian Borntraeger <borntraeger@de.ibm.com>,
kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org,
Heiko Carstens <heiko.carstens@de.ibm.com>
Subject: Re: [PATCH] s390/qeth: fix spelling mistake "alocpool" -> "allocpool"
Date: Thu, 12 Sep 2019 08:22:12 +0100 [thread overview]
Message-ID: <e5b3aff1-9017-d169-1a8a-22a4d58efcb4@canonical.com> (raw)
In-Reply-To: <de37e3a5-faad-44ae-32b2-d7c6c5d3732d@linux.ibm.com>
On 12/09/2019 08:19, Ursula Braun wrote:
>
>
> On 9/11/19 5:35 PM, Colin King wrote:
>> From: Colin Ian King <colin.king@canonical.com>
>>
>> There is a spelling mistake in QETH_CARD_TEXT text. Fix it.
>>
>
> This spelling mistake is intended, because this qeth trace area is defined for
> 8 byte length entries. We try to make the entries as speaking as possible - even
> at cost of spelling mistakes.
Ah, OK.
>
>> Signed-off-by: Colin Ian King <colin.king@canonical.com>
>> ---
>> drivers/s390/net/qeth_core_main.c | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/drivers/s390/net/qeth_core_main.c b/drivers/s390/net/qeth_core_main.c
>> index a7868c8133ee..ab96b22db3fe 100644
>> --- a/drivers/s390/net/qeth_core_main.c
>> +++ b/drivers/s390/net/qeth_core_main.c
>> @@ -218,7 +218,7 @@ static int qeth_alloc_buffer_pool(struct qeth_card *card)
>> void *ptr;
>> int i, j;
>>
>> - QETH_CARD_TEXT(card, 5, "alocpool");
>> + QETH_CARD_TEXT(card, 5, "allocpool");
>> for (i = 0; i < card->qdio.init_pool.buf_count; ++i) {
>> pool_entry = kzalloc(sizeof(*pool_entry), GFP_KERNEL);
>> if (!pool_entry) {
>>
>
prev parent reply other threads:[~2019-09-12 7:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-11 15:35 [PATCH] s390/qeth: fix spelling mistake "alocpool" -> "allocpool" Colin King
2019-09-12 7:19 ` Ursula Braun
2019-09-12 7:22 ` Colin Ian King [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=e5b3aff1-9017-d169-1a8a-22a4d58efcb4@canonical.com \
--to=colin.king@canonical.com \
--cc=borntraeger@de.ibm.com \
--cc=gor@linux.ibm.com \
--cc=heiko.carstens@de.ibm.com \
--cc=jwi@linux.ibm.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=ubraun@linux.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