From: Greg KH <gregkh@linuxfoundation.org>
To: Tudor.Ambarus@microchip.com
Cc: alexander.levin@microsoft.com, stable@vger.kernel.org,
herbert@gondor.apana.org.au, hulkci@huawei.com, lkp@intel.com,
yuehaibing@huawei.com
Subject: Re: [PATCH 5.4] crypto: atmel - Fix build error of CRYPTO_AUTHENC
Date: Wed, 15 Jul 2020 14:22:05 +0200 [thread overview]
Message-ID: <20200715122205.GB2937397@kroah.com> (raw)
In-Reply-To: <d8246e0c-2948-c9d8-e4b0-fb3581ec5983@microchip.com>
On Wed, Jul 15, 2020 at 11:37:47AM +0000, Tudor.Ambarus@microchip.com wrote:
> On 7/15/20 12:20 PM, Greg KH wrote:
> > EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe
> >
> > On Wed, Jul 15, 2020 at 11:38:02AM +0300, Tudor Ambarus wrote:
> >> Backport to 5.4.52-rc1 the following commits in upstream:
> >> commit aee1f9f3c30e1e20e7f74729ced61eac7d74ca68 upstream.
> >> commit d158367682cd822aca811971e988be6a8d8f679f upstream.
> >
> > Please backport the individual commits, do not squash them together.
> > That way lies problems as it is hard to track and almost always
> > incorrect.
> >
>
> d158367682cd822aca811971e988be6a8d8f679f attempted to fix the problem,
> but it was just papering it. The real fix is in
> aee1f9f3c30e1e20e7f74729ced61eac7d74ca68. I kept references to both
> commits for tracking reasons.
>
> Please let me know if you still want me to backport both in dedicated
> patches, or maybe to just drop the reference to
> d158367682cd822aca811971e988be6a8d8f679f
No, please backport both, as a patch series.
thanks,
greg k-h
prev parent reply other threads:[~2020-07-15 12:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-15 8:38 [PATCH 5.4] crypto: atmel - Fix build error of CRYPTO_AUTHENC Tudor Ambarus
2020-07-15 9:20 ` Greg KH
2020-07-15 11:37 ` Tudor.Ambarus
2020-07-15 12:22 ` Greg KH [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=20200715122205.GB2937397@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=Tudor.Ambarus@microchip.com \
--cc=alexander.levin@microsoft.com \
--cc=herbert@gondor.apana.org.au \
--cc=hulkci@huawei.com \
--cc=lkp@intel.com \
--cc=stable@vger.kernel.org \
--cc=yuehaibing@huawei.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