mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Linux regression tracking #adding (Thorsten Leemhuis)"  <regressions@leemhuis.info>
To: Bastian Krause <bst@pengutronix.de>,
	meenakshi.aggarwal@nxp.com, horia.geanta@nxp.com,
	V.sethi@nxp.com, pankaj.gupta@nxp.com, gaurav.jain@nxp.com,
	herbert@gondor.apana.org.au, davem@davemloft.net,
	linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: Victoria Milhoan <vicki.milhoan@freescale.com>,
	Dan Douglass <dan.douglass@nxp.com>,
	Vipul Kumar <vipul_kumar@mentor.com>,
	kernel@pengutronix.de,
	Linux kernel regressions list <regressions@lists.linux.dev>
Subject: Re: [PATCH] crypto: caam - adjust RNG timing to support more devices
Date: Sat, 5 Aug 2023 15:04:19 +0200	[thread overview]
Message-ID: <0ca063c6-eaa2-0123-21cb-65d4a33550f4@leemhuis.info> (raw)
In-Reply-To: <e1f3f073-9d5e-1bae-f4f8-08dc48adad62@pengutronix.de>

[CCing the regression list, as it should be in the loop for regressions:
https://docs.kernel.org/admin-guide/reporting-regressions.html]

[TLDR: I'm adding this report to the list of tracked Linux kernel
regressions; the text you find below is based on a few templates
paragraphs you might have encountered already in similar form.
See link in footer if these mails annoy you.]

On 17.07.23 14:43, Bastian Krause wrote:
> On 6/12/23 10:26, meenakshi.aggarwal@nxp.com wrote:
>> From: Victoria Milhoan <vicki.milhoan@freescale.com>
>>
>> Adjust RNG timing parameters to support more i.MX6 devices.
>>
>> Signed-off-by: Victoria Milhoan <vicki.milhoan@freescale.com>
>> Signed-off-by: Dan Douglass <dan.douglass@nxp.com>
>> Signed-off-by: Vipul Kumar <vipul_kumar@mentor.com>
>> Signed-off-by: Horia Geantă <horia.geanta@nxp.com>
>> ---
>>   drivers/crypto/caam/ctrl.c | 4 ++--
>>   1 file changed, 2 insertions(+), 2 deletions(-)
> 
> This patch seems to breaks CAAM RNG instantiation on an i.MX8MM at my end:
> [...]

Thanks for the report. I see that people are working on it already. But
to be sure the issue doesn't fall through the cracks unnoticed, I'm
adding it to regzbot, the Linux kernel regression tracking bot:

#regzbot ^introduced ef492d08030
#regzbot title crypto: broke CAAM RNG instantiation on an i.MX8MM
#regzbot ignore-activity

This isn't a regression? This issue or a fix for it are already
discussed somewhere else? It was fixed already? You want to clarify when
the regression started to happen? Or point out I got the title or
something else totally wrong? Then just reply and tell me -- ideally
while also telling regzbot about it, as explained by the page listed in
the footer of this mail.

Developers: When fixing the issue, remember to add 'Link:' tags pointing
to the report (the parent of this mail). See page linked in footer for
details.

Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)
--
Everything you wanna know about Linux kernel regression tracking:
https://linux-regtracking.leemhuis.info/about/#tldr
That page also explains what to do if mails like this annoy you.


      parent reply	other threads:[~2023-08-05 13:04 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-12  8:26 meenakshi.aggarwal
2023-06-15 11:45 ` Gaurav Jain
2023-06-23  8:20 ` Herbert Xu
2023-07-17 12:43 ` Bastian Krause
2023-07-18  9:43   ` Bastian Krause
2023-07-19  7:00     ` Meenakshi Aggarwal
2023-07-24  5:13       ` Meenakshi Aggarwal
2023-08-04  9:14         ` Herbert Xu
2023-08-04 12:02           ` [EXT] " Gaurav Jain
2023-08-11  8:47             ` Linux regression tracking (Thorsten Leemhuis)
2023-08-11 11:55               ` Meenakshi Aggarwal
2023-08-11 12:58                 ` Meenakshi Aggarwal
2023-08-13 14:04                   ` Linux regression tracking (Thorsten Leemhuis)
2023-07-24 17:21       ` Bastian Krause
2023-08-05 13:04   ` Linux regression tracking #adding (Thorsten Leemhuis) [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=0ca063c6-eaa2-0123-21cb-65d4a33550f4@leemhuis.info \
    --to=regressions@leemhuis.info \
    --cc=V.sethi@nxp.com \
    --cc=bst@pengutronix.de \
    --cc=dan.douglass@nxp.com \
    --cc=davem@davemloft.net \
    --cc=gaurav.jain@nxp.com \
    --cc=herbert@gondor.apana.org.au \
    --cc=horia.geanta@nxp.com \
    --cc=kernel@pengutronix.de \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=meenakshi.aggarwal@nxp.com \
    --cc=pankaj.gupta@nxp.com \
    --cc=regressions@lists.linux.dev \
    --cc=vicki.milhoan@freescale.com \
    --cc=vipul_kumar@mentor.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

all inboxes | Powered by JetHome®