From: Shawn Guo <shawnguo@kernel.org>
To: lkp@lists.01.org
Subject: Re: [scatterlist] c38ecfb12e: kernel BUG at crypto/scatterwalk.c:37!
Date: Wed, 13 Apr 2016 10:38:50 +0800 [thread overview]
Message-ID: <20160413023850.GF28903@tiger> (raw)
In-Reply-To: <20160413014202.GA659@yexl-desktop>
[-- Attachment #1: Type: text/plain, Size: 475 bytes --]
On Wed, Apr 13, 2016 at 09:42:02AM +0800, kernel test robot wrote:
> FYI, we noticed the below changes on
>
> https://github.com/0day-ci/linux Shawn-Guo/scatterlist-use-sg_dma_len-in-sg_set_page/20160411-105225
> commit c38ecfb12e9a4c0c17d0879090741d6ce2a200de ("scatterlist: use sg_dma_len() in sg_set_page()")
Yes, the patch is wrong, and has been discarded. The patch should
really be tagged with RFC from the beginning. Thanks for reporting
anyway.
Shawn
WARNING: multiple messages have this Message-ID (diff)
From: Shawn Guo <shawnguo@kernel.org>
To: kernel test robot <xiaolong.ye@intel.com>
Cc: 0day robot <fengguang.wu@intel.com>,
LKML <linux-kernel@vger.kernel.org>,
lkp@01.org
Subject: Re: [lkp] [scatterlist] c38ecfb12e: kernel BUG at crypto/scatterwalk.c:37!
Date: Wed, 13 Apr 2016 10:38:50 +0800 [thread overview]
Message-ID: <20160413023850.GF28903@tiger> (raw)
In-Reply-To: <20160413014202.GA659@yexl-desktop>
On Wed, Apr 13, 2016 at 09:42:02AM +0800, kernel test robot wrote:
> FYI, we noticed the below changes on
>
> https://github.com/0day-ci/linux Shawn-Guo/scatterlist-use-sg_dma_len-in-sg_set_page/20160411-105225
> commit c38ecfb12e9a4c0c17d0879090741d6ce2a200de ("scatterlist: use sg_dma_len() in sg_set_page()")
Yes, the patch is wrong, and has been discarded. The patch should
really be tagged with RFC from the beginning. Thanks for reporting
anyway.
Shawn
next prev parent reply other threads:[~2016-04-13 2:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-13 1:42 [scatterlist] c38ecfb12e: kernel BUG at crypto/scatterwalk.c:37! kernel test robot
2016-04-13 1:42 ` [lkp] " kernel test robot
2016-04-13 2:38 ` Shawn Guo [this message]
2016-04-13 2:38 ` Shawn Guo
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=20160413023850.GF28903@tiger \
--to=shawnguo@kernel.org \
--cc=lkp@lists.01.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 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.