public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: Asai Thambi S P <asamymuthupa@micron.com>
Cc: David Milburn <dmilburn@redhat.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mtip32xx: dynamically allocate buffer in debugfs functions
Date: Tue, 17 Sep 2013 12:21:50 -0600	[thread overview]
Message-ID: <52389DBE.8050901@kernel.dk> (raw)
In-Reply-To: <52389D12.4090109@micron.com>

On 09/17/2013 12:18 PM, Asai Thambi S P wrote:
> On 07/12/2013 3:59 PM, Asai Thambi S P wrote:
>> On 5/23/2013 2:23 PM, David Milburn wrote:
>>
>>> Dynamically allocate buf to prevent warnings:
>>>
>>> drivers/block/mtip32xx/mtip32xx.c: In function
>>> ‘mtip_hw_read_device_status’:
>>> drivers/block/mtip32xx/mtip32xx.c:2823: warning: the frame size of
>>> 1056 bytes is larger than 1024 bytes
>>> drivers/block/mtip32xx/mtip32xx.c: In function ‘mtip_hw_read_registers’:
>>> drivers/block/mtip32xx/mtip32xx.c:2894: warning: the frame size of
>>> 1056 bytes is larger than 1024 bytes
>>> drivers/block/mtip32xx/mtip32xx.c: In function ‘mtip_hw_read_flags’:
>>> drivers/block/mtip32xx/mtip32xx.c:2917: warning: the frame size of
>>> 1056 bytes is larger than 1024 bytes
>>>
>>> Signed-off-by: David Milburn <dmilburn@redhat.com>
>>
>> Acked-by: Asai Thambi S P <asamymuthupa@micron.com>
>>
> Jens,
> 
> Please include this patch too for 3.12.

Queued up.

-- 
Jens Axboe


      reply	other threads:[~2013-09-17 18:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-23 21:23 [PATCH] mtip32xx: dynamically allocate buffer in debugfs functions David Milburn
2013-07-12 22:59 ` Asai Thambi S P
2013-09-17 18:18   ` Asai Thambi S P
2013-09-17 18:21     ` Jens Axboe [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=52389DBE.8050901@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=asamymuthupa@micron.com \
    --cc=dmilburn@redhat.com \
    --cc=linux-kernel@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