[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAONX=-f=qnUqVCTuotrEp6MCMk_f+wWj4FPY6skXHHWuitqZiQ@mail.gmail.com>
Date: Fri, 29 Jul 2022 18:37:02 +1000
From: Daniil Lunev <dlunev@...omium.org>
To: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Cc: Adrian Hunter <adrian.hunter@...el.com>,
Bart Van Assche <bvanassche@....org>,
Alim Akhtar <alim.akhtar@...sung.com>,
Andy Gross <agross@...nel.org>,
Avri Altman <avri.altman@....com>,
Bean Huo <beanhuo@...ron.com>,
Bjorn Andersson <bjorn.andersson@...aro.org>,
Daejun Park <daejun7.park@...sung.com>,
Eric Biggers <ebiggers@...gle.com>,
"James E.J. Bottomley" <jejb@...ux.ibm.com>,
Konrad Dybcio <konrad.dybcio@...ainline.org>,
"Martin K. Petersen" <martin.petersen@...cle.com>,
Matthias Brugger <matthias.bgg@...il.com>,
Mike Snitzer <snitzer@...hat.com>,
Stanley Chu <stanley.chu@...iatek.com>,
Ulf Hansson <ulf.hansson@...aro.org>,
linux-arm-kernel@...ts.infradead.org,
linux-arm-msm@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-mediatek@...ts.infradead.org, linux-scsi@...r.kernel.org
Subject: Re: [PATCH v3 1/2] ufs: add function to check CRYPTO capability
> This is not a valid changelog text, sorry. Please read the
> documentation for how to write a valid one.
Sorry for that. Though the latest patchset is v4 and that one
doesn't contain this patch since Eric Biggers pointed out the
crypto information can be obtained from device's queue sysfs
node. But I will try to be better further on.
> Something went wrong with your patch, there is no --- line, so git will
> apply it with the diffstat, right?
>
> Did you hand-edit this?
Hm, I don't recall hand editing it, but the possibility of pilot error is
always there. I am still getting used to the upstream tooling and
processes. Sorry for the inconvenience, but as I mentioned, this
patch is dropped in v4 version (and sorry for high traffic of changes
on this patchset)
Thanks,
Daniil
Powered by blists - more mailing lists