Delete local variable "u8 sec_idx" because is declared and set, but never
used.
Signed-off-by: Fabio M. De Francesco
---
drivers/staging/rtl8723bs/core/rtw_ieee80211.c | 4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
diff --git a/drivers/staging/rtl8723bs/core/rtw_ieee80211.c
On Fri, 2021-04-09 at 22:09 +0200, Peter Zijlstra wrote:
> On Fri, Apr 09, 2021 at 03:21:49PM -0400, David Malcolm wrote:
> > [Caveat: I'm a gcc developer, not a kernel expert]
> >
> > But it's not *quite* a global constant, or presumably you would be
> > simply using a global constant, right?
Hi soc maintainers,
Please merge the following new changes for soc/fsl drivers.
Regards,
Leo
The following changes since commit a38fd8748464831584a19438cbb3082b5a2dab15:
Linux 5.12-rc2 (2021-03-05 17:33:41 -0800)
are available in the Git repository at:
On Wed, Mar 31, 2021 at 6:54 PM Borislav Petkov wrote:
>
> On Wed, Mar 31, 2021 at 06:28:27PM -0400, Len Brown wrote:
> > dynamic XCR0 breaks the installed base, I thought we had established
> > that.
>
> We should do a clear cut and have legacy stuff which has its legacy
> expectations on the
On 4/9/21 3:53 AM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 4.19.186 release.
There are 18 patches in this series, all will be posted as a response
to this one. If anyone has any issues with these being applied, please
let me know.
Responses should be made
IMPORTANT NOTE FOR REVIEWERS: Andrew has removed Oscar Salvador's series
"Make alloc_contig_range handle Hugetlb pages" so that this series can
go in first. Most issues discussed in v4 of this series do not apply
until Oscar's series is added and will be addressed then. This could be
more
free_pool_huge_page was called with hugetlb_lock held. It would remove
a hugetlb page, and then free the corresponding pages to the lower level
allocators such as buddy. free_pool_huge_page was called in a loop to
remove hugetlb pages and these loops could hold the hugetlb_lock for a
Commit c77c0a8ac4c5 ("mm/hugetlb: defer freeing of huge pages if in
non-task context") was added to address the issue of free_huge_page
being called from irq context. That commit hands off free_huge_page
processing to a workqueue if !in_task. However, this doesn't cover
all the cases as pointed
With the introduction of remove_hugetlb_page(), there is no need for
update_and_free_page to hold the hugetlb lock. Change all callers to
drop the lock before calling.
With additional code modifications, this will allow loops which decrease
the huge page pool to drop the hugetlb_lock with each
After making hugetlb lock irq safe and separating some functionality
done under the lock, add some lockdep_assert_held to help verify
locking.
Signed-off-by: Mike Kravetz
Acked-by: Michal Hocko
Reviewed-by: Miaohe Lin
Reviewed-by: Muchun Song
Reviewed-by: Oscar Salvador
---
mm/hugetlb.c | 9
Now that cma_release is non-blocking and irq safe, there is no need to
drop hugetlb_lock before calling.
Signed-off-by: Mike Kravetz
Acked-by: Roman Gushchin
Acked-by: Michal Hocko
Reviewed-by: Oscar Salvador
Reviewed-by: David Hildenbrand
---
mm/hugetlb.c | 6 --
1 file changed, 6
The new remove_hugetlb_page() routine is designed to remove a hugetlb
page from hugetlbfs processing. It will remove the page from the active
or free list, update global counters and set the compound page
destructor to NULL so that PageHuge() will return false for the 'page'.
After this call, the
The helper routine hstate_next_node_to_alloc accesses and modifies the
hstate variable next_nid_to_alloc. The helper is used by the routines
alloc_pool_huge_page and adjust_pool_surplus. adjust_pool_surplus is
called with hugetlb_lock held. However, alloc_pool_huge_page can not
be called with
cma_release is currently a sleepable operatation because the bitmap
manipulation is protected by cma->lock mutex. Hugetlb code which relies
on cma_release for CMA backed (giga) hugetlb pages, however, needs to be
irq safe.
The lock doesn't protect any sleepable operation so it can be changed to
a
On Wed, Mar 31, 2021 at 6:45 PM Andy Lutomirski wrote:
>
> On Wed, Mar 31, 2021 at 3:28 PM Len Brown wrote:
>
> > We added compiler annotation for user-level interrupt handlers.
> > I'm not aware of it failing, or otherwise being confused.
>
> I followed your link and found nothing. Can you
Hi Alex,
I love your patch! Yet something to improve:
[auto build test ERROR on robh/for-next]
[also build test ERROR on v5.12-rc6 next-20210409]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https
On Thu, Apr 8, 2021 at 7:58 PM Huang, Ying wrote:
>
> Yang Shi writes:
>
> > On Thu, Apr 8, 2021 at 10:19 AM Shakeel Butt wrote:
> >>
> >> Hi Tim,
> >>
> >> On Mon, Apr 5, 2021 at 11:08 AM Tim Chen
> >> wrote:
> >> >
> >> > Traditionally, all memory is DRAM. Some DRAM might be closer/faster
On Fri, Apr 9, 2021 at 8:54 PM Jakub Kicinski wrote:
>
> On Fri, 9 Apr 2021 20:06:04 +0200 Matteo Croce wrote:
> > From: Matteo Croce
> >
> > use the new helper macro skb_for_each_frag() which allows to iterate
> > through all the SKB fragments.
> >
> > The patch was created with Coccinelle,
On 4/8/21 10:05 PM, Andrew Morton wrote:
> On Thu, 8 Apr 2021 09:11:30 +0200 Oscar Salvador wrote:
>
>> But if It is going to be easier for Andrew, just pull them all out and I
>> will resend the whole series once this work goes in.
>
> I think so.
>
> I shall drop these:
>
>
Recently added memfd_secret() syscall had a flags parameter passed
as unsigned long, which requires creation of compat entry for it.
It was possible to change the type of flags to unsigned int and so
avoid bothering with compat layer.
https://www.spinics.net/lists/linux-mm/msg251550.html
On Sat, 10 Apr 2021, Mitali Borkar wrote:
> No changes required in this patch.
> In v1:- Added spaces around '<<' operator to improve readability and meet
> linux kernel coding
> style
The text above would go in the git history. "No changes required in this
patch." doesn't make sense in
Add support for the SC7280 SoC, which includes IPA version 4.11.
Signed-off-by: Alex Elder
---
drivers/net/ipa/Makefile | 2 +-
drivers/net/ipa/ipa_data-v4.11.c | 382 +++
drivers/net/ipa/ipa_data.h | 1 +
drivers/net/ipa/ipa_main.c | 4 +
4
Checksum offload for IPA v4.5+ is implemented differently, using
"inline" offload (which uses a common header format for both upload
and download offload).
The IPA hardware must be programmed to enable MAP checksum offload,
but the RMNet driver is responsible for interpreting checksum
metadata
Add support for the SDX55 SoC, which includes IPA version 4.5.
Starting with IPA v4.5, a few of the memory regions have a different
number of "canary" values; update comments in the where the region
identifers are defined to accurately reflect that.
I'll note three differences in SDX55 versus
Add existing supported platform "qcom,sc7180-ipa" to the set of IPA
compatible strings. Also add newly-supported "qcom,sdx55-ipa",
"qcom,sc7280-ipa".
Signed-off-by: Alex Elder
---
Documentation/devicetree/bindings/net/qcom,ipa.yaml | 6 +-
1 file changed, 5 insertions(+), 1 deletion(-)
This series adds IPA support for two more Qualcomm SoCs.
The first patch updates the DT binding to add compatible strings.
The second temporarily disables checksum offload support for IPA
version 4.5 and above. Changes are required to the RMNet driver
to support the "inline" checksum offload
On Fri, 9 Apr 2021 22:01:51 +0300
Ilias Apalodimas wrote:
> On Fri, Apr 09, 2021 at 11:56:48AM -0700, Jakub Kicinski wrote:
> > On Fri, 2 Apr 2021 20:17:31 +0200 Matteo Croce wrote:
> > > Co-developed-by: Jesper Dangaard Brouer
> > > Co-developed-by: Matteo Croce
> > > Signed-off-by: Ilias
On 4/9/21 3:53 AM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 5.4.111 release.
There are 23 patches in this series, all will be posted as a response
to this one. If anyone has any issues with these being applied, please
let me know.
Responses should be
On 4/9/21 3:53 AM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 5.10.29 release.
There are 41 patches in this series, all will be posted as a response
to this one. If anyone has any issues with these being applied, please
let me know.
Responses should be made
On 4/9/21 3:53 AM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 5.11.13 release.
There are 45 patches in this series, all will be posted as a response
to this one. If anyone has any issues with these being applied, please
let me know.
Responses should be made
The dwc2 driver has everything we need to run
in ACPI mode except for the ACPI module device table
boilerplate. With that added and identified as "BCM2848",
an id in use by other OSs for this device, the dw2
controller on the BCM2711 will work.
Signed-off-by: Jeremy Linton
---
Hi Lee,
On Tue, Apr 6, 2021 at 1:54 PM Lee Jones wrote:
> > > These have been on the list for a couple of weeks now.
thanks for your fixes, I've gone through them now. I've fixed up some
comments instead of "demoting" them to make the patch somewhat less
destructive, and I found a few more
On 4/9/2021 2:53 AM, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 4.9.266 release.
> There are 13 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
>
> Responses
On Fri, Apr 09, 2021 at 12:29:29PM -0700, Jakub Kicinski wrote:
> On Fri, 9 Apr 2021 22:01:51 +0300 Ilias Apalodimas wrote:
> > On Fri, Apr 09, 2021 at 11:56:48AM -0700, Jakub Kicinski wrote:
> > > On Fri, 2 Apr 2021 20:17:31 +0200 Matteo Croce wrote:
> > > > Co-developed-by: Jesper Dangaard
On 4/9/2021 12:32 PM, Konrad Rzeszutek Wilk wrote:
> On Thu, Apr 08, 2021 at 08:13:07PM -0700, Florian Fainelli wrote:
>>
>>
>> On 3/24/2021 1:42 AM, Christoph Hellwig wrote:
>>> On Mon, Mar 22, 2021 at 06:53:49PM -0700, Florian Fainelli wrote:
When SWIOTLB_NO_FORCE is used, there should
On Thu, 8 Apr 2021 18:32:36 +0530, Vijendar Mukunda wrote:
> Add ALC1015p codec support for acp3x machine driver.
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next
Thanks!
[1/1] ASoC: amd: Add support for ALC1015P codec in acp3x machine driver
Could you retest this against the latest drm-tip? I pushed something that I
think might fix this
On Thu, 2021-03-25 at 21:53 +0800, Oliver Sang wrote:
> Hi, Lyude,
>
> On Tue, Mar 23, 2021 at 01:27:29PM -0400, Lyude Paul wrote:
> > BTW Oliver - I'm still happy to look at this issue, I just need
On 4/9/2021 3:19 PM, Borislav Petkov wrote:
> On Fri, Apr 09, 2021 at 02:45:23PM -0500, Saripalli, RK wrote:
>> Yes, these options should be fine for now.
>> Like you said, if we get the need to add prctl and seccomp, I can always do
>> that later.
>>
>> What do you think auto should default
On Fri, Apr 9, 2021 at 1:14 AM Paolo Bonzini wrote:
>
> On 09/04/21 03:18, James Bottomley wrote:
> > If you want to share ASIDs you have to share the firmware that the
> > running VM has been attested to. Once the VM moves from LAUNCH to
> > RUNNING, the PSP won't allow the VMM to inject any
On 4/9/21 2:00 PM, Shuah Khan wrote:
On 4/9/21 2:58 AM, Suravee Suthikulpanit wrote:
In early AMD desktop/mobile platforms (during 2013), when the IOMMU
Performance Counter (PMC) support was first introduced in
commit 30861ddc9cca ("perf/x86/amd: Add IOMMU Performance Counter
resource
On Fri, Apr 09, 2021 at 02:45:23PM -0500, Saripalli, RK wrote:
> Yes, these options should be fine for now.
> Like you said, if we get the need to add prctl and seccomp, I can always do
> that later.
>
> What do you think auto should default to?.
> In SSBD case, I believe auto defaults to prctl
On Fri, Apr 09, 2021 at 11:53:26AM +0200, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 5.11.13 release.
> There are 45 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me
On Fri, Apr 09, 2021 at 11:53:22AM +0200, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 5.10.29 release.
> There are 41 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me
On Fri, Apr 09, 2021 at 11:53:30AM +0200, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 5.4.111 release.
> There are 23 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me
On 4/9/21 9:51 PM, Sudip Mukherjee wrote:
On Fri, Apr 09, 2021 at 11:54:01AM +0200, Greg Kroah-Hartman wrote:
From: Piotr Krysiuk
commit 26f55a59dc65ff77cd1c4b37991e26497fc68049 upstream.
I am not finding this in Linus's tree and even not seeing this change in
master branch also. Am I
On Fri, Apr 09, 2021 at 11:53:28AM +0200, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 4.19.186 release.
> There are 18 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me
The variable ret is being initialized as 0 and is never used until
it's updated by sdio_register_driver()
This removes the redundant initialization of ret
Signed-off-by: Bryan Brattlof
---
drivers/staging/rtl8723bs/os_dep/sdio_intf.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff
On Fri, Apr 09, 2021 at 11:53:25AM +0200, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 4.14.230 release.
> There are 14 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me
From: Arnd Bergmann
Using no_printk() for jbd_debug() revealed two warnings:
fs/jbd2/recovery.c: In function 'fc_do_one_pass':
fs/jbd2/recovery.c:256:30: error: format '%d' expects a matching 'int' argument
[-Werror=format=]
256 | jbd_debug(3, "Processing fast commit blk with
On Fri, Apr 09, 2021 at 12:33:29PM -0700, Nick Desaulniers wrote:
> On Fri, Apr 9, 2021 at 4:18 AM Peter Zijlstra wrote:
> >
> > On Fri, Apr 09, 2021 at 12:55:18PM +0200, Florian Weimer wrote:
> > > * Ard Biesheuvel:
> > >
> > > > Wouldn't that require the compiler to interpret the contents of
On Sat, 10 Apr 2021, Mitali Borkar wrote:
> Removed comments from the same line and added them to new line above the
> blocks, aligned everything properly by using tabs to make code neater
> and improve readability.
>
> Signed-off-by: Mitali Borkar
> ---
>
On 09/04/2021 09:58, Suravee Suthikulpanit wrote:
In early AMD desktop/mobile platforms (during 2013), when the IOMMU
Performance Counter (PMC) support was first introduced in
commit 30861ddc9cca ("perf/x86/amd: Add IOMMU Performance Counter
resource management"), there was a HW bug where the
On Fri, Apr 9, 2021 at 8:50 AM Dave Hansen wrote:
>
> On 4/8/21 11:17 AM, Oscar Salvador wrote:
> > --- a/mm/page_alloc.c
> > +++ b/mm/page_alloc.c
> > @@ -8490,7 +8490,8 @@ static int __alloc_contig_migrate_range(struct
> > compact_control *cc,
> > cc->nr_migratepages -=
On Fri, Apr 09, 2021 at 03:21:49PM -0400, David Malcolm wrote:
> [Caveat: I'm a gcc developer, not a kernel expert]
>
> But it's not *quite* a global constant, or presumably you would be
> simply using a global constant, right? As the optimizer gets smarter,
> you don't want to have it one day
On Fri, Apr 9, 2021 at 11:08 AM Nicolas Saenz Julienne
wrote:
>
> For testing purposes this driver might be built on big-endian
> architectures. So make sure we take that into account when populating
> structures that are to be passed to RPi4's mailbox.
>
> Reported-by: kernel test robot
>
The pull request you sent on Fri, 9 Apr 2021 15:00:09 -0500:
> git://git.kernel.org/pub/scm/linux/kernel/git/robh/linux.git
> tags/devicetree-fixes-for-5.12-2
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/a2521822bdfd73bd40d7cd81dfa89cc922b1cff4
Thank you!
--
On Fri, Apr 09, 2021 at 11:53:20AM +0200, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 4.9.266 release.
> There are 13 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me
On Fri, Apr 09, 2021 at 11:53:06AM +0200, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 4.4.266 release.
> There are 20 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me
On Fri, Apr 09, 2021 at 12:38:59AM +0200, Frederic Weisbecker wrote:
> Once srcu_init() is called, the SRCU core is free to queue delayed
> workqueues, which rely on timers. However init_timers() is called
> several steps after rcu_init(). Any call_srcu() in-between would finish
> its course
On 4/9/21 2:58 AM, Suravee Suthikulpanit wrote:
In early AMD desktop/mobile platforms (during 2013), when the IOMMU
Performance Counter (PMC) support was first introduced in
commit 30861ddc9cca ("perf/x86/amd: Add IOMMU Performance Counter
resource management"), there was a HW bug where the
Hello:
This patch was applied to netdev/net.git (refs/heads/master):
On Fri, 9 Apr 2021 08:42:23 +0100 you wrote:
> Some trivial spelling mistakes which caught my eye during the
> review of the code.
>
> Signed-off-by: Salil Mehta
> ---
>
Hello:
This patch was applied to netdev/net.git (refs/heads/master):
On Thu, 8 Apr 2021 20:39:04 -0400 you wrote:
> From: Sven Van Asbroeck
>
> The ethernet frame length is calculated incorrectly. Depending on
> the value of RX_HEAD_PADDING, this may result in ethernet frames
> that are too
Linus,
Please pull. This has the fix for the OpenRisc regression Guenter
reported.
Rob
The following changes since commit b5a95bb1883e2bac1009cc88e65c71cff6f931e6:
dt-bindings: media: Use graph and video-interfaces schemas, round 2
(2021-03-01 11:30:21 -0600)
are available in the Git
The pull request you sent on Fri, 9 Apr 2021 13:44:38 -0400:
> git://git.kernel.org/pub/scm/linux/kernel/git/pcmoore/selinux.git
> tags/selinux-pr-20210409
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/60144b23c94216b4aca6fba90dca9349183f39e1
Thank you!
--
The pull request you sent on Fri, 9 Apr 2021 18:27:04 +0200:
> git://git.kernel.org/pub/scm/linux/kernel/git/xen/tip.git
> for-linus-5.12b-rc7-tag
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/0b76088799cc8db1ea9c626e54e7bc65f605e65f
Thank you!
--
Deet-doot-dot,
The pull request you sent on Fri, 9 Apr 2021 17:44:47 +0200:
> git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git
> acpi-5.12-rc7
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/ccd6c35c72c771616c37d1978e02a982da0678ef
Thank you!
--
Deet-doot-dot, I
The pull request you sent on Sat, 10 Apr 2021 05:46:21 +1000:
> git://anongit.freedesktop.org/drm/drm tags/drm-fixes-2021-04-10
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/a85f165e1f38c0a5a6e671ce8126a8cafe35af09
Thank you!
--
Deet-doot-dot, I am a bot.
The pull request you sent on Fri, 9 Apr 2021 12:48:16 -0400:
> https://git.kernel.org/pub/scm/linux/kernel/git/mst/vhost.git tags/for_linus
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/189fefc7a4f0401d0f799de96b772319a6541fc1
Thank you!
--
Deet-doot-dot, I am a
The pull request you sent on Fri, 9 Apr 2021 11:07:58 -0500:
> https://git.kernel.org/pub/scm/linux/kernel/git/andersson/remoteproc.git
> tags/rproc-v5.12-fixes
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/3766fcf5d318046e0ae58659e03ead35d40cb9dd
Thank you!
--
>-Original Message-
>From: Yongxin Liu
>Sent: Monday, March 22, 2021 12:15 AM
>To: vaibhavgupt...@gmail.com; andrewx.bow...@intel.com; Nguyen, Anthony
>L
>Cc: net...@vger.kernel.org; linux-kernel@vger.kernel.org;
>da...@davemloft.net; Brandeburg, Jesse ; intel-
Hi Greg,
On Fri, Apr 09, 2021 at 11:54:00AM +0200, Greg Kroah-Hartman wrote:
> From: Piotr Krysiuk
>
> commit e4d4d456436bfb2fe412ee2cd489f7658449b098 upstream.
And, this one also. I am unable to find this SHA in Linus's tree.
--
Regards
Sudip
Hi Greg,
On Fri, Apr 09, 2021 at 11:54:01AM +0200, Greg Kroah-Hartman wrote:
> From: Piotr Krysiuk
>
> commit 26f55a59dc65ff77cd1c4b37991e26497fc68049 upstream.
I am not finding this in Linus's tree and even not seeing this change in
master branch also. Am I missing something?
--
Regards
Hey Linus,
Was relatively quiet this week, but still a few pulls came in, pretty
much small fixes across the board, a couple of regression fixes in the
amdgpu/radeon code, msm has a few minor fixes across the board, a
panel regression fix also.
I'm out all next week, so Daniel will do any last
On 4/9/21 12:02 PM, Andy Shevchenko wrote:
kernel.h is being used as a dump for all kinds of stuff for a long time.
Here is the attempt to start cleaning it up by splitting out panic and
oops helpers.
There are several purposes of doing this:
- dropping dependency in bug.h
- dropping a loop by
Boris, thank you.
On 4/9/2021 2:39 PM, Borislav Petkov wrote:
> On Fri, Apr 09, 2021 at 01:22:49PM -0500, Saripalli, RK wrote:
>>> And I think you don't need this one either if we do a "light" controls
>>> thing but lemme look at the rest first.
>
> Ok, and what I mean with "lite" version is
On Fri, Apr 9, 2021 at 7:00 PM Mitali Borkar wrote:
>
> Looks good, will try this.
if you re-send this patch then please include our mailing list:
linux-amlo...@lists.infradead.org
Thank you!
Martin
syzbot wrote:
> Hello,
>
> syzbot found the following issue on:
>
> HEAD commit:9c54130c Add linux-next specific files for 20210406
> git tree: linux-next
> console output: https://syzkaller.appspot.com/x/log.txt?x=17d8d7aad0
> kernel config:
Hello Vladimir,
On Fri, Apr 9, 2021 at 12:46 AM Vladimir Oltean wrote:
>
> On Thu, Apr 08, 2021 at 08:38:27PM +0200, Martin Blumenstingl wrote:
> > PHY auto polling on the GSWIP hardware can be used so link changes
> > (speed, link up/down, etc.) can be detected automatically. Internally
> >
On Fri, Apr 09, 2021 at 12:21:28PM -0700, Nathan Chancellor wrote:
> With the latest mkimage from U-Boot 2021.04, the generic defconfigs no
> longer build, failing with:
>
> /usr/bin/mkimage: verify_header failed for FIT Image support with exit code 1
>
> This is expected after the linked
On Fri, Apr 09, 2021 at 01:22:49PM -0500, Saripalli, RK wrote:
> > And I think you don't need this one either if we do a "light" controls
> > thing but lemme look at the rest first.
Ok, and what I mean with "lite" version is something like this below
which needs finishing and testing.
Initially,
On Fri, Apr 9, 2021 at 6:56 PM Sven Peter wrote:
> On Wed, Apr 7, 2021, at 12:44, Will Deacon wrote:
> > On Sun, Mar 28, 2021 at 09:40:07AM +0200, Sven Peter wrote:
> >
> > > + cfg->pgsize_bitmap &= SZ_16K;
> > > + if (!cfg->pgsize_bitmap)
> > > + return NULL;
> >
> > This is
On Fri, Apr 9, 2021 at 12:26 PM Rob Herring wrote:
>
> On Wed, Apr 7, 2021 at 3:45 PM Ilya Lipnitskiy
> wrote:
> >
> > On Tue, Apr 6, 2021 at 6:24 PM Saravana Kannan wrote:
> > >
> > > On Tue, Apr 6, 2021 at 6:10 PM Rob Herring wrote:
> > > >
> > > > On Tue, Apr 6, 2021 at 7:46 PM Saravana
On Fri, Apr 09, 2021 at 09:41:06PM +0300, Radu Pirea (NXP OSS) wrote:
> Add driver for tja1103 driver and for future NXP C45 PHYs.
So apart from c45 vs c22, how does this differ to nxp-tja11xx.c?
Do we really want two different drivers for the same hardware?
Can we combine them somehow?
>
On Fri, Apr 9, 2021 at 4:18 AM Peter Zijlstra wrote:
>
> On Fri, Apr 09, 2021 at 12:55:18PM +0200, Florian Weimer wrote:
> > * Ard Biesheuvel:
> >
> > > Wouldn't that require the compiler to interpret the contents of the
> > > asm() block?
> >
> > Yes and no. It would require proper toolchain
On Thu, Apr 08, 2021 at 08:13:07PM -0700, Florian Fainelli wrote:
>
>
> On 3/24/2021 1:42 AM, Christoph Hellwig wrote:
> > On Mon, Mar 22, 2021 at 06:53:49PM -0700, Florian Fainelli wrote:
> >> When SWIOTLB_NO_FORCE is used, there should really be no allocations of
> >> default_nslabs to occur
On Fri, 9 Apr 2021 21:41:06 +0300 Radu Pirea (NXP OSS) wrote:
> Add driver for tja1103 driver and for future NXP C45 PHYs.
>
> Signed-off-by: Radu Pirea (NXP OSS)
drivers/net/phy/nxp-c45: struct mdio_device_id is 8 bytes. The last of 1 is:
0x10 0xb0 0x1b 0x00 0xf0 0xff 0xff 0xff
FATAL:
On Fri, 9 Apr 2021 22:01:51 +0300 Ilias Apalodimas wrote:
> On Fri, Apr 09, 2021 at 11:56:48AM -0700, Jakub Kicinski wrote:
> > On Fri, 2 Apr 2021 20:17:31 +0200 Matteo Croce wrote:
> > > Co-developed-by: Jesper Dangaard Brouer
> > > Co-developed-by: Matteo Croce
> > > Signed-off-by: Ilias
On 4/9/21 12:56 PM, David Laight wrote:
From: Chris von Recklinghausen
Sent: 08 April 2021 11:46
Suspend fails on a system in fips mode because md5 is used for the e820
integrity check and is not available. Use crc32 instead.
Prior to this patch, MD5 is used only to create a digest to ensure
On Fri, Apr 09, 2021 at 01:25:26AM CDT, Zev Weiss wrote:
>On Fri, Apr 09, 2021 at 12:59:09AM CDT, Andrew Jeffery wrote:
>>
>>
>>On Fri, 9 Apr 2021, at 13:27, Zev Weiss wrote:
>>>On Fri, Mar 19, 2021 at 01:27:41AM CDT, Andrew Jeffery wrote:
Make the KCS device drivers responsible for allocating
On Wed, Apr 7, 2021 at 3:45 PM Ilya Lipnitskiy
wrote:
>
> On Tue, Apr 6, 2021 at 6:24 PM Saravana Kannan wrote:
> >
> > On Tue, Apr 6, 2021 at 6:10 PM Rob Herring wrote:
> > >
> > > On Tue, Apr 6, 2021 at 7:46 PM Saravana Kannan
> > > wrote:
> > > >
> > > > On Tue, Apr 6, 2021 at 5:34 PM Rob
On 4/9/2021 11:37 AM, Jakub Kicinski wrote:
On Fri, 9 Apr 2021 20:01:14 +0300 Vadym Kochan wrote:
On Fri, Apr 09, 2021 at 09:51:13AM -0700, Samudrala, Sridhar wrote:
On 4/9/2021 9:22 AM, Oleksandr Mazur wrote:
I'd like to discuss a possibility of handling devlink port parameters
with devlink
Add reset_method sysfs attribute to enable user to
query and set user preferred device reset methods and
their ordering.
Reviewed-by: Alex Williamson
Reviewed-by: Raphael Norwitz
Co-developed-by: Alex Williamson
Signed-off-by: Alex Williamson
Signed-off-by: Amey Narkhede
---
reset_fn field is used to indicate whether the
device supports any reset mechanism or not.
Deprecate use of reset_fn in favor of new
reset_methods array which can be used to keep
track of all supported reset mechanisms of a device
and their ordering.
The octeon driver is incorrectly using reset_fn
Introduce a new array reset_methods in struct pci_dev
to keep track of reset mechanisms supported by the
device and their ordering. Also refactor probing and reset
functions to take advantage of calling convention of reset
functions.
Reviewed-by: Alex Williamson
Reviewed-by: Raphael Norwitz
Currently there is separate function pcie_has_flr to probe
if pcie flr is supported by the device which does not match
the calling convention followed by reset methods which use second
function argument to decide whether to probe or not.
Add new function pcie_reset_flr that follows the calling
From: Raphael Norwitz
Slot resets are bus resets with additional logic to prevent a device
from being removed during the reset. Currently slot and bus resets have
separate implementations in pci.c, complicating higher level logic. As
discussed on the mailing list, they should be combined into a
PCI and PCIe devices may support a number of possible reset mechanisms
for example Function Level Reset (FLR) provided via Advanced Feature or
PCIe capabilities, Power Management reset, bus reset, or device specific reset.
Currently the PCI subsystem creates a policy prioritizing these reset
On Fri, 09 Apr 2021 14:47:47 +0200, Mauro Carvalho Chehab wrote:
> Changeset 1ca9d1b1342d ("dt-bindings:iio:adc:motorola,cpcap-adc yaml
> conversion")
> renamed: Documentation/devicetree/bindings/iio/adc/cpcap-adc.txt
> to: Documentation/devicetree/bindings/iio/adc/motorola,cpcap-adc.yaml.
>
>
On Fri, Apr 09, 2021 at 12:48:21AM CDT, Andrew Jeffery wrote:
>
>
>On Fri, 9 Apr 2021, at 13:26, Zev Weiss wrote:
>> On Fri, Mar 19, 2021 at 01:27:40AM CDT, Andrew Jeffery wrote:
>> >Take steps towards defining a coherent API to separate the KCS device
>> >drivers from the userspace interface.
On 4/9/2021 2:53 AM, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 5.4.111 release.
> There are 23 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
>
> Responses
201 - 300 of 1578 matches
Mail list logo
