mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Michal Simek <michal.simek@xilinx.com>
To: Arnd Bergmann <arnd@kernel.org>, Michal Simek <michal.simek@xilinx.com>
Cc: Rajan Vaja <rajan.vaja@xilinx.com>, Arnd Bergmann <arnd@arndb.de>,
	"Linux ARM" <linux-arm-kernel@lists.infradead.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	<TEJASP@xilinx.com>,
	Amit Sunil Dhamne <amit.sunil.dhamne@xilinx.com>,
	Ravi Patel <ravi.patel@xilinx.com>
Subject: Re: [PATCH] firmware: xilinx: Use hash-table for api feature check
Date: Tue, 24 Nov 2020 14:04:46 +0100	[thread overview]
Message-ID: <40c98156-36d4-6b2c-a7ed-ef736fda9544@xilinx.com> (raw)
In-Reply-To: <CAK8P3a37YhCPmzJMi2iw=XQwx2_7r1ueCF6AA_j7qkCJV05Uuw@mail.gmail.com>

Hi,

On 24. 11. 20 14:02, Arnd Bergmann wrote:
> On Tue, Nov 24, 2020 at 1:54 PM Michal Simek <michal.simek@xilinx.com> wrote:
>> On 24. 11. 20 6:52, Rajan Vaja wrote:
>>
>> Some lines should be added.
>>
>> Cc: stable <stable@vger.kernel.org>
>> Fixes: f3217d6f2f7a ("firmware: xilinx: fix out-of-bounds access")
>>
>> Tested-by: Michal Simek <michal.simek@xilinx.com>
> 
> Reviewed-by: Arnd Bergmann <arnd@arndb.de>
> 
>> Arnd: do you see any issue with this?
>> I found that your origin patch was taken by Greg and pushed to any
>> 5.10-rc version which caused panic on Xilinx Versal. That's why I would
>> like to get this patch to v5.10 if possible.
> 
> Looks ok to me. If you'd like me to pick it up through the soc fixes
> branch, please forward with the above tags to soc@kernel.org

I have one more fix in my queue. Will send pull request with it soon.

Thanks,
Michal

  reply	other threads:[~2020-11-24 13:04 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-24  5:52 Rajan Vaja
2020-11-24 12:54 ` Michal Simek
2020-11-24 13:02   ` Arnd Bergmann
2020-11-24 13:04     ` Michal Simek [this message]
2020-11-24 14:25 ` Michal Simek

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=40c98156-36d4-6b2c-a7ed-ef736fda9544@xilinx.com \
    --to=michal.simek@xilinx.com \
    --cc=TEJASP@xilinx.com \
    --cc=amit.sunil.dhamne@xilinx.com \
    --cc=arnd@arndb.de \
    --cc=arnd@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rajan.vaja@xilinx.com \
    --cc=ravi.patel@xilinx.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®