From: Zhang AiHua <zhangaihua1@huawei.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: <tytso@mit.edu>, <linux-ext4@vger.kernel.org>, <stable@vger.kernel.org>
Subject: Re: [PATCH] fix compile error while opening the macro DOUBLE_CHECK
Date: Tue, 17 Nov 2015 14:31:14 +0800 [thread overview]
Message-ID: <564AC9B2.8040106@huawei.com> (raw)
In-Reply-To: <20151117040305.GA10663@kroah.com>
Hi,
I want to submit the patch to mainline, I feel so ashamed for disturbing you,
you can ignore it.... I have written wrong email.
Later, when I need, I will read Documentation/stable_kernel_rules.txt first,
thank you anyway.
Regards, AiHua.
在 2015/11/17 12:03, Greg KH 写道:
> On Tue, Nov 17, 2015 at 11:04:03AM +0800, zhangaihua1@huawei.com wrote:
>> From: Aihua Zhang <zhangaihua1@huawei.com>
>>
>> the error is:
>> fs/ext4/mballoc.c:475:43: error: 'struct ext4_group_info' has
>> no member named 'bb_bitmap'
>> the definition of macro should before 'struct ext4_group_info'
>>
>> Signed-off-by: Aihua Zhang <zhangaihua1@huawei.com>
>> ---
>> fs/ext4/ext4.h | 12 ++++++++++++
>> fs/ext4/mballoc.h | 12 ------------
>> 2 files changed, 12 insertions(+), 12 deletions(-)
>
> <formletter>
>
> This is not the correct way to submit patches for inclusion in the
> stable kernel tree. Please read Documentation/stable_kernel_rules.txt
> for how to do this properly.
>
> </formletter>
>
> .
>
next prev parent reply other threads:[~2015-11-17 6:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-17 3:04 [PATCH] fix compile error while opening the macro DOUBLE_CHECK zhangaihua1
2015-11-17 3:26 ` kbuild test robot
2015-11-17 4:03 ` Greg KH
2015-11-17 6:31 ` Zhang AiHua [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-11-17 3:52 zhangaihua1
2015-12-01 8:58 zhangaihua1
2016-03-13 21:19 ` Theodore Ts'o
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=564AC9B2.8040106@huawei.com \
--to=zhangaihua1@huawei.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-ext4@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=tytso@mit.edu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.