From: Greg KH <gregkh@linuxfoundation.org>
To: linux-aspeed@lists.ozlabs.org
Subject: [PATCH v3] usb: gadget: aspeed_udc: Add check for dma_alloc_coherent
Date: Sat, 24 Dec 2022 07:37:32 +0100 [thread overview]
Message-ID: <Y6aeLMAu+XCYTxt6@kroah.com> (raw)
In-Reply-To: <20221224025001.24503-1-jiasheng@iscas.ac.cn>
On Sat, Dec 24, 2022 at 10:50:01AM +0800, Jiasheng Jiang wrote:
> Yes, it is the same as mine.
> As the previous patch had not been merged into the Linux kernel,
> my tool found the same error and report it.
> And both of us chose the most concise way to fix the error.
> That is why the patches are the same.
I have no context at all here, what does this refer to?
confused,
greg k-h
WARNING: multiple messages have this Message-ID (diff)
From: Greg KH <gregkh@linuxfoundation.org>
To: Jiasheng Jiang <jiasheng@iscas.ac.cn>
Cc: neal_liu@aspeedtech.com, joel@jms.id.au, andrew@aj.id.au,
sumit.semwal@linaro.org, christian.koenig@amd.com,
linux-aspeed@lists.ozlabs.org, linux-usb@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-media@vger.kernel.org,
dri-devel@lists.freedesktop.org, linaro-mm-sig@lists.linaro.org
Subject: Re: [PATCH v3] usb: gadget: aspeed_udc: Add check for dma_alloc_coherent
Date: Sat, 24 Dec 2022 07:37:32 +0100 [thread overview]
Message-ID: <Y6aeLMAu+XCYTxt6@kroah.com> (raw)
In-Reply-To: <20221224025001.24503-1-jiasheng@iscas.ac.cn>
On Sat, Dec 24, 2022 at 10:50:01AM +0800, Jiasheng Jiang wrote:
> Yes, it is the same as mine.
> As the previous patch had not been merged into the Linux kernel,
> my tool found the same error and report it.
> And both of us chose the most concise way to fix the error.
> That is why the patches are the same.
I have no context at all here, what does this refer to?
confused,
greg k-h
WARNING: multiple messages have this Message-ID (diff)
From: Greg KH <gregkh@linuxfoundation.org>
To: Jiasheng Jiang <jiasheng@iscas.ac.cn>
Cc: neal_liu@aspeedtech.com, joel@jms.id.au, andrew@aj.id.au,
sumit.semwal@linaro.org, christian.koenig@amd.com,
linux-aspeed@lists.ozlabs.org, linux-usb@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-media@vger.kernel.org,
dri-devel@lists.freedesktop.org, linaro-mm-sig@lists.linaro.org
Subject: Re: [PATCH v3] usb: gadget: aspeed_udc: Add check for dma_alloc_coherent
Date: Sat, 24 Dec 2022 07:37:32 +0100 [thread overview]
Message-ID: <Y6aeLMAu+XCYTxt6@kroah.com> (raw)
In-Reply-To: <20221224025001.24503-1-jiasheng@iscas.ac.cn>
On Sat, Dec 24, 2022 at 10:50:01AM +0800, Jiasheng Jiang wrote:
> Yes, it is the same as mine.
> As the previous patch had not been merged into the Linux kernel,
> my tool found the same error and report it.
> And both of us chose the most concise way to fix the error.
> That is why the patches are the same.
I have no context at all here, what does this refer to?
confused,
greg k-h
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
WARNING: multiple messages have this Message-ID (diff)
From: Greg KH <gregkh@linuxfoundation.org>
To: Jiasheng Jiang <jiasheng@iscas.ac.cn>
Cc: linux-aspeed@lists.ozlabs.org, andrew@aj.id.au,
neal_liu@aspeedtech.com, linux-usb@vger.kernel.org,
linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
sumit.semwal@linaro.org, linaro-mm-sig@lists.linaro.org,
joel@jms.id.au, christian.koenig@amd.com,
linux-arm-kernel@lists.infradead.org,
linux-media@vger.kernel.org
Subject: Re: [PATCH v3] usb: gadget: aspeed_udc: Add check for dma_alloc_coherent
Date: Sat, 24 Dec 2022 07:37:32 +0100 [thread overview]
Message-ID: <Y6aeLMAu+XCYTxt6@kroah.com> (raw)
In-Reply-To: <20221224025001.24503-1-jiasheng@iscas.ac.cn>
On Sat, Dec 24, 2022 at 10:50:01AM +0800, Jiasheng Jiang wrote:
> Yes, it is the same as mine.
> As the previous patch had not been merged into the Linux kernel,
> my tool found the same error and report it.
> And both of us chose the most concise way to fix the error.
> That is why the patches are the same.
I have no context at all here, what does this refer to?
confused,
greg k-h
next prev parent reply other threads:[~2022-12-24 6:37 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-24 2:50 [PATCH v3] usb: gadget: aspeed_udc: Add check for dma_alloc_coherent Jiasheng Jiang
2022-12-24 2:50 ` Jiasheng Jiang
2022-12-24 2:50 ` Jiasheng Jiang
2022-12-24 6:37 ` Greg KH [this message]
2022-12-24 6:37 ` Greg KH
2022-12-24 6:37 ` Greg KH
2022-12-24 6:37 ` Greg KH
-- strict thread matches above, loose matches on Subject: below --
2022-12-24 7:35 Jiasheng Jiang
2022-12-24 7:35 ` Jiasheng Jiang
2022-12-24 7:35 ` Jiasheng Jiang
2022-12-15 12:31 Jiasheng Jiang
2022-12-15 12:31 ` Jiasheng Jiang
2022-12-15 12:31 ` Jiasheng Jiang
2022-12-15 12:31 ` Jiasheng Jiang
2022-12-23 14:54 ` Greg KH
2022-12-23 14:54 ` Greg KH
2022-12-23 14:54 ` Greg KH
2022-12-23 14:54 ` Greg KH
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=Y6aeLMAu+XCYTxt6@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=linux-aspeed@lists.ozlabs.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.