erved_1[8];
> };
> }
Note, such a thing would only be for the distros that want it, you can
add support for this to the tool, but there is no need for any
__kabi_reserved fields in mainline.
> Here gendwarfksyms would see the __kabi_reserved prefix and only use
> u8 [8] for the CRC
s the commit _after_ this one that turns on the
taint for the build :)
anyway, nice work, I think it's almost there!
greg k-h
ernel development is done through emails, not calls :)
If a submitter isn't willing to maintain the code they submit, then it
should be rejected as maintance is the most important part.
Sorry,
greg k-h
On Thu, Jul 04, 2024 at 08:16:34PM +0900, Yunseong Kim wrote:
> Hi Greg, Hi Jakub
>
> On 7/4/24 6:32 오후, Greg Kroah-Hartman wrote:
> > On Wed, Jul 03, 2024 at 07:18:35PM -0700, Jakub Kicinski wrote:
> >> On Wed, 3 Jul 2024 03:01:47 +0900 Yunseong Kim wrote:
> >&
applied the patch, tested it again, and confirmed
> > working fine.
>
> You're missing the customary "[ Upstream commit ]"
> line, not sure Greg will pick this up.
>
Yeah, I missed this, needs to be very obvious what is happening here.
I'll replace the version in the queues with this one now, thanks.
greg k-h
On Wed, Jun 19, 2024 at 01:50:36AM +0900, Masahiro Yamada wrote:
> On Wed, Jun 19, 2024 at 1:44 AM Greg Kroah-Hartman
> wrote:
> >
> > On Mon, Jun 17, 2024 at 05:58:19PM +, Sami Tolvanen wrote:
> > > Hi folks,
> > >
> > > This series impleme
mainly
> because of the existing support for C host tools that use elfutils
> (e.g., objtool).
That's cool, can the C code be switched to also use this? That way we
only have one path/code for all of this?
thanks,
greg k-h
On Mon, Jun 10, 2024 at 10:44:42AM -0700, Dan Williams wrote:
> Greg Kroah-Hartman wrote:
> > Now that the driver core allows for struct class to be in read-only
> > memory, we should make all 'class' structures declared at build time
> > placing them into read-only memo
ed-by: Steven Rostedt (Google)
> >
> > Do we have a way to add a "Depends-on" tag so that anyone backporting this
> > will know that it requires the change to whatever allowed that to happen?
>
> Looks like people use that tag, although no grep hits in Documentation, so
> Cc'ing workflows@ and Thorsten.
>
> In this case it would be
>
> Depends-on: c9929f0e344a ("mm/slob: remove CONFIG_SLOB")
Ick, no, use the documented way of handling this as described in the
stable kernel rules file.
thanks,
greg k-h
Cc: nvd...@lists.linux.dev
Signed-off-by: Greg Kroah-Hartman
---
drivers/nvdimm/bus.c | 19 ++-
1 file changed, 10 insertions(+), 9 deletions(-)
diff --git a/drivers/nvdimm/bus.c b/drivers/nvdimm/bus.c
index 508aed017ddc..101c425f3e8b 100644
--- a/drivers/nvdimm/bus.c
+++ b
verted that commit to 6.9.2 and now it only serves the trace but
> the panic is gone. But I can live with it.
Steven, should we revert that?
Or is there some other change that we should take to resolve this?
thanks,
greg k-h
On Tue, May 14, 2024 at 06:21:57PM -0700, Yuanchu Xie wrote:
> On Tue, May 14, 2024 at 9:06 AM Greg Kroah-Hartman
> wrote:
> >
> > On Mon, May 13, 2024 at 07:03:00PM -0700, Yuanchu Xie wrote:
> > > Memctl provides a way for the guest to control its physical memory
&g
mctl_vmm_call);
You export something that is never actually called, which implies that
this is not tested at all (i.e. it is dead code.) Please remove.
Also, why not EXPORT_SYMBOL_GPL()? (I have to ask, sorry.)
thanks,
greg k-h
esp;
Endain-ness of all of this as it goes to the hardware, right?
> + };
> + u32 command;
> +};
> +
> +struct memctl_percpu_channel {
> + struct memctl_buf buf;
> + u64 buf_phys_addr;
> + u32 command;
> +};
> +
> +struct memctl {
> + void __iomem *base_addr;
> + /* cache the info call */
> + struct memctl_vmm_info memctl_vmm_info;
> + struct memctl_percpu_channel __percpu *pcpu_channels;
> +};
> +
> +static DEFINE_RWLOCK(memctl_lock);
> +static struct memctl *memctl __read_mostly;
> +
> +static void memctl_write_command(void __iomem *base_addr, u32 command)
> +{
> + iowrite32(command,
> + base_addr + offsetof(struct memctl_transport, command));
Yup, you write this to hardware, please use proper structures and types
for that, otherwise you will have problems in the near future.
thanks,
greg k-h
_MAX is larger than PERF_MAX_TRACE_SIZE
> (2048 before the patch), the warning will trigger.
>
> The fix was included in 5.16, so backporting to 5.15 and earlier LTS
> kernels. Also included is a patch that better describes the attempted
> allocation size.
All now queued up, thanks.
greg k-h
On Mon, Apr 22, 2024 at 10:46:37PM +0100, Mauro Carvalho Chehab wrote:
> Em Mon, 22 Apr 2024 15:25:18 -0400
> Konstantin Ryabitsev escreveu:
>
> > On Mon, Apr 22, 2024 at 05:49:29PM +0200, Thorsten Leemhuis wrote:
> > > @Greg, BTW: should this be stable+noau
onsider no functions a failure too.
>*/
> if (!ret) {
> ret = -ENOENT;
>
> Cc: sta...@kernel.org # 5.15, 5.10, 5.4, 4.19
> Signed-off-by: Siddh Raman Pant
> ---
> kernel/trace/trace_events_trigger.c | 6 ++
> 1 file changed, 2 insertions(+), 4 deletions(-)
Now queued up everywhere, thanks.
greg k-h
On Thu, Apr 18, 2024 at 09:04:53AM +0200, Thorsten Leemhuis wrote:
> On 17.04.24 15:38, Greg KH wrote:
> > On Wed, Apr 17, 2024 at 03:21:12PM +0200, Thorsten Leemhuis wrote:
> >> On 17.04.24 14:52, Konstantin Ryabitsev wrote:
> >>> On Wed, Apr 17, 2024 at 09:48:18AM
able-autosel: ignore
> > [This fix requires a feature that is only present in mainline]
> >
> > This allows passing along structured information that can be parsed by
> > automated tooling without putting it into the commit.
>
> That afaics makes them
t's the
simpler and more explicit thing to do for those that do not want to have
anything backported they do not explicitly mark as such (some subsystems
do this already, like kvm and -mm and xfs, it's fine!). This all is
here because of maintainers who do NOT want to do that.
thanks,
greg k-h
way? If I need to file a
> ticket somewhere or some ack from a higher authority, just let me know!
I approve this message :)
thanks,
greg k-h
mment to
/proc/bootconfig")
Signed-off-by: Zhenhua Huang
Signed-off-by: Paul E. McKenney
Cc:
Cc:
Cc: sta...@vger.kernel.org
Acked-by: Masami Hiramatsu (Google)
Signed-off-by: Masami Hiramatsu (Google)
Signed-off-by: Greg Kroah-Hartman
---
fs/proc/bootconfig.c | 12 ++--
1 file c
p ignoring -EEXIST
> > errors.
> >
> > Fixes: e17e0f51aeea ("Driver core: show drivers in /sys/module/")
> > Reviewed-by: Greg Kroah-Hartman
>
> Reviewed-by: Luis Chamberlain
Oh right, I should apply this, sorry about that, will go do that now...
rly unwind and return the error code to the
> caller. My reading of the original code was that it tries to
> not fail when the links already exist, so keep ignoring -EEXIST
> errors.
>
> Cc: Luis Chamberlain
> Cc: linux-modu...@vger.kernel.org
> Cc: Greg Kroah-Hartman
>
rly unwind and return the error code to the
> caller. My reading of the original code was that it tries to
> not fail when the links already exist, so keep ignoring -EEXIST
> errors.
>
> Cc: Luis Chamberlain
> Cc: linux-modu...@vger.kernel.org
> Cc: Greg Kroah-Hartman
>
o void to prevent this check as well.
>
> Cc: Luis Chamberlain
> Cc: linux-modu...@vger.kernel.org
> Cc: Greg Kroah-Hartman
> Cc: "Rafael J. Wysocki"
> Fixes: e17e0f51aeea ("Driver core: show drivers in /sys/module/")
> See-also: 4a7fb6363f2d ("add __
t Red Hat and CVEs, they know how to
let us know about stuff like this, but no. Hopefully, someday soon,
they will soon not be allowed to do this anymore.
{sigh}
Now queued up, thanks.
greg k-h
On Wed, Feb 07, 2024 at 12:20:00AM +0100, Luca Weiss wrote:
> On Tue Jan 2, 2024 at 2:53 PM CET, Greg Kroah-Hartman wrote:
> > On Tue, Jan 02, 2024 at 02:43:24PM +0100, Luca Weiss wrote:
> > > On Tue Jan 2, 2024 at 2:36 PM CET, Greg Kroah-Hartman wrote:
> > > > On T
On Sun, Feb 04, 2024 at 01:07:11PM -0300, Ricardo B. Marliere wrote:
> Now that the driver core can properly handle constant struct bus_type,
> move the dax_bus_type variable to be a constant structure as well,
> placing it into read-only memory which can not be modified at runtime.
>
.
>
> Cc: Greg Kroah-Hartman
> Suggested-by: Greg Kroah-Hartman
> Signed-off-by: Ricardo B. Marliere
Reviewed-by: Greg Kroah-Hartman
On Sun, Feb 04, 2024 at 05:32:05PM -0300, Ricardo B. Marliere wrote:
> Now that the driver core can properly handle constant struct bus_type,
> move the rpmsg_bus variable to be a constant structure as well,
> placing it into read-only memory which can not be modified at runtime.
>
On Sun, Feb 04, 2024 at 05:50:45PM -0300, Ricardo B. Marliere wrote:
> Now that the driver core can properly handle constant struct bus_type,
> move the vdpa_bus variable to be a constant structure as well,
> placing it into read-only memory which can not be modified at runtime.
>
On Sun, Feb 04, 2024 at 05:52:51PM -0300, Ricardo B. Marliere wrote:
> Now that the driver core can properly handle constant struct bus_type,
> move the virtio_bus variable to be a constant structure as well,
> placing it into read-only memory which can not be modified at runtime.
>
On Thu, Feb 01, 2024 at 01:08:23PM -0500, Steven Rostedt wrote:
> On Thu, 1 Feb 2024 10:05:59 -0800
> Greg KH wrote:
>
> > > timerlat_fd =
> > > open("/sys/kernel/tracing/osnoise/per_cpu/cpu0/timerlat_fd", 'r')
> > > timerlat_fd.close();
&g
On Thu, Feb 01, 2024 at 05:02:56PM +0100, Daniel Bristot de Oliveira wrote:
> On 2/1/24 16:44, Greg KH wrote:
> > On Thu, Feb 01, 2024 at 04:13:39PM +0100, Daniel Bristot de Oliveira wrote:
> >> Currently, the timerlat's hrtimer is initialized at the first read of
> >>
ng.
What error exactly happens? Userspace, or the kernel crashes?
thanks,
greg k-h
data supplies[ANX7688_NUM_SUPPLIES];
> + struct power_supply *vbus_in_supply;
> + struct notifier_block vbus_in_nb;
> + int input_current_limit; // mA
> +struct gpio_desc *gpio_enable;
> +struct gpio_desc *gpio_reset;
> +struct gpio_desc *gpio_cabledet;
I'm stopping here, again, tabs, you know this :(
greg k-h
go back and guess in the future, that isn't nice.
thanks,
greg k-h
On Wed, Jan 31, 2024 at 05:16:09PM +, John Garry wrote:
> On 31/01/2024 16:22, Greg KH wrote:
> > > before:
> > > real0m53.591s
> > > user1m1.842s
> > > sys 0m9.161s
> > >
> > > after:
> > > real0m37.481s
&
also convert more UTS_RELEASE users to prove this is proper
> approach.
I like it, I also think that v4l2 includes this as well as all of those
drivers seem to rebuild when this changes, does that not happen for you
too?
Anyway, if the firmware changes work, I'm all for this, thanks for
taking it on!
thanks,
greg k-h
> to the
> > dev_pm_domain_attach_list(). I decided not to, but please let me know if you
> > prefer the other option.
> >
> > Note 3)
> > For OPP integration, as a follow up I am striving to make the
> > dev_pm_opp_attach_genpd() redundant. Instead I think we shoul
On Tue, Jan 02, 2024 at 02:43:24PM +0100, Luca Weiss wrote:
> On Tue Jan 2, 2024 at 2:36 PM CET, Greg Kroah-Hartman wrote:
> > On Thu, Dec 21, 2023 at 02:45:26PM +0100, Luca Weiss wrote:
> > > On Thu Dec 21, 2023 at 1:53 PM CET, Konrad Dybcio wrote:
> > > > On 21.1
t; > >>> So from my POV qcm6490 makes more sense
> > >>
> > >> But yeah since it's likely that sc7280 firmware behaves the same as
> > >> qcm6490 firmware it's probably okay to use sc7280 compatible, worst case
> > >> we change it later :) I'll send a v2 with those changes.
> > >
> > > Worst case we end up with sc7280 which has yet another slightly
> > > different UCSI / PMIC GLINK implementation, but the compatible string
> > > is already taken.
> > > I still suppose that this should be a qcm6490-related string.
> > Right, let's keep qcm then
>
> Ack from my side also. Thanks for the feedback!
This doesn't apply to my tree, where should it be going through?
thanks,
greg k-h
>
> - return sprintf(buf, "%llu\n", size);
> + return sprintf(buf, "%llu\n", dax_region_avail_size(dax_region));
sysfs_emit() everywhere please.
But again, the issue is "why do you need a lock"?
thanks,
greg k-h
ishal Verma
> Cc: Ira Weiny
> Cc: Peter Zijlstra
> Cc: Greg Kroah-Hartman
> Cc: Andrew Morton
> Signed-off-by: Dan Williams
> ---
> Hi Greg,
>
> I wonder if you might include this change in v6.7-rc to ease some patch
> sets alternately going through my tree and Andr
of a dax region.
> +
> +What:/sys/bus/dax/devices/daxX.Y/memmap_on_memory
> +Date: October, 2023
It's not October anymore :)
thanks,
greg k-h
On Tue, Nov 28, 2023 at 08:05:26AM +, Greg KH wrote:
> On Mon, Nov 27, 2023 at 11:27:07AM -0800, Matthew Maurer wrote:
> > > > >
> > > > > > With regards to future directions that likely won't work for
> > > > > > loosening it:
> > &
el needs to be fixed up to support this
> > properly, not just ignored like this patchset does.
> I agree there is a divergence here, I tried to point it out so that it
> wouldn't be
> a surprise later. The .rmeta file itself (which is the only way we
> could know that
> the ABI act
just an update to the new stable 5.10.201
> > version and no RT changes have been made.
> >
> > You can get this release via the git tree at:
> >
> > git://git.kernel.org/pub/scm/linux/kernel/git/rt/linux-stable-rt.git
> >
> > branch: v5.10-rt
> &g
On Fri, Nov 24, 2023 at 01:59:24PM +0100, Vlastimil Babka wrote:
> +Cc workflows
>
> On 11/24/23 12:43, Greg Kroah-Hartman wrote:
> > On Thu, Nov 23, 2023 at 07:20:46PM +0100, Oleksandr Natalenko wrote:
> >> Hello.
> >>
> >> Since v6.6.2 kernel release
On Thu, Nov 23, 2023 at 08:38:45PM +0900, Masahiro Yamada wrote:
> On Thu, Nov 23, 2023 at 6:05 PM Greg KH wrote:
> >
> > On Wed, Nov 22, 2023 at 01:04:09PM -0800, Matthew Maurer wrote:
> > > > So, even if you enable CONFIG_MODVERSIONS,
> > > > nothin
u to consider this useful? If not, can you help me understand
> what level of precision would be required?
What exactly does .rmeta have to do with the function signature? That's
all you care about here.
thanks,
greg k-h
Again, this needs to be broken into much smaller pieces before we can
even review it. Would you want to review this?
thanks,
greg "think of the reviewers" k-h
a series.
thanks,
greg k-h
On Wed, Nov 01, 2023 at 08:54:56PM +0530, Naresh Kamboju wrote:
> Hi Greg,
>
> I see the following build warning / errors everywhere on stable-rc 5.15
> branch.
>
> ld.lld: error: undefined symbol: kallsyms_on_each_symbol
> >>> referenced by trace_kpro
; Signed-off-by: Arnd Bergmann
Reviewed-by: Greg Kroah-Hartman
drivers/staging/rtl8192u/r8192U_core.c| 109
> 6 files changed, 729 deletions(-)
Reviewed-by: Greg Kroah-Hartman
removed as well.
>
> Looking through the exported functions, I found a bunch more that have
> no callers, so just drop all of those.
>
> Signed-off-by: Arnd Bergmann
Reviewed-by: Greg Kroah-Hartman
aging/rtl8712/os_intfs.c| 1 -
> drivers/staging/rtl8712/osdep_intf.h | 2 -
> drivers/staging/rtl8712/rtl871x_ioctl_linux.c | 124 --
> 3 files changed, 127 deletions(-)
Reviewed-by: Greg Kroah-Hartman
Signed-off-by: Greg Kroah-Hartman
---
tools/testing/nvdimm/test/ndtest.c | 17 +
tools/testing/nvdimm/test/nfit.c | 14 +++---
2 files changed, 16 insertions(+), 15 deletions(-)
diff --git a/tools/testing/nvdimm/test/ndtest.c
b/tools/testing/nvdimm/test/ndtest.c
index
is cleared up.
Reported-by: Prarit Bhargava
Cc: Christoph Hellwig
Cc: Vitaly Kuznetsov
Cc: jsch...@samba.org
Signed-off-by: Greg Kroah-Hartman
---
.../device_drivers/appletalk/cops.rst | 80 --
.../device_drivers/appletalk/index.rst| 18 -
.../networking/device_drivers/index.rst
On Wed, Sep 27, 2023 at 03:46:30PM +0900, Justin Stitt wrote:
> On Wed, Sep 27, 2023 at 3:14 PM Greg KH wrote:
> >
> > On Wed, Sep 27, 2023 at 03:19:16AM +, Justin Stitt wrote:
> > > Note that folks really shouldn't be using get_maintainer on tree files
> >
m.
So please don't take that valid use-case away from us.
thanks,
greg k-h
ser left. The best might be to indeed just
> remove it and see if anyone screams, in which case we could bring it
> back after doing the above.
>
We should just remove them for now, I have no objection to that at all.
Want me to send the patch?
thanks,
greg k-h
operation, such as load
> situation and CPU busy/idle status
The cpu that is printing the log isn't the one that added the log
message, so I think you will have incorrect data here, right?
thanks,
greg k-h
On Fri, Sep 15, 2023 at 03:40:34PM +0800, Enlin Mu wrote:
> From: Enlin Mu
>
> Sometimes we want to print cpu id of printk() messages to consoles
This is rejected every few years. What has changes from the previous
times this was sent?
And why can't you use trace_printk()?
thanks,
greg k-h
dead code elimination in the
> CONFIG_PROVE_LOCKING=n case.
>
> Suggested-by: Peter Zijlstra
> Cc: Greg Kroah-Hartman
> Cc: "Rafael J. Wysocki"
> Cc: Ingo Molnar
> Cc: Will Deacon
> Cc: Waiman Long
> Cc: Boqun Feng
> Cc: Alison Schofield
> Cc: Vishal V
Link:
> https://lore.kernel.org/r/ylf0dewci8myl...@hirez.programming.kicks-ass.net [1]
> Cc: Greg Kroah-Hartman
> Cc: "Rafael J. Wysocki"
> Suggested-by: Peter Zijlstra
> Signed-off-by: Dan Williams
YES!
Acked-by: Greg Kroah-Hartman
Nice work.
On Tue, Apr 20, 2021 at 01:47:17PM +, Nava kishore Manne wrote:
> Hi Greg,
>
> Please find my response inline.
>
> > -Original Message-----
> > From: Greg KH
> > Sent: Tuesday, April 20, 2021 2:21 PM
> > To: Nava kishore Manne
> > Cc
On Tue, Apr 20, 2021 at 01:36:51PM +, Nava kishore Manne wrote:
> Hi Greg,
>
> Please find my response inline.
>
> > -Original Message-----
> > From: Greg KH
> > Sent: Tuesday, April 20, 2021 2:17 PM
> > To: Nava kishore Manne
> > Cc
return -EINVAL;
> + }
> + ret = zynqmp_pm_afi(reg, val);
> + if (ret < 0) {
> + dev_err(>dev, "AFI register write error %d\n",
> + ret);
> + return ret;
> + }
> + }
> + return 0;
> +}
Again, why does this have to be in the kernel? All it does is make a
single call to the hardware based on some values read from the device
tree. Can't you do this from userspace?
thanks,
greg k-h
+ the proper Bus-width values
Please use tabs properly, you mix them above, checkpatch should have
caught that.
thanks,
greg k-h
_CTRL_OFFSET);
> + reg_val = readl(afi_fpga->membase + AFI_WRCHAN_CTRL_OFFSET);
> + reg_val &= ~AFI_BUSWIDTH_MASK;
> + writel(reg_val | afi_fpga->afi_width,
> +afi_fpga->membase + AFI_WRCHAN_CTRL_OFFSET);
> +
> + return 0;
> +}
I do not understand, why is this driver needed at all? Why can't you do
the above from userspace?
All this does is write some values to the hardware at probe time, who
needs this?
thanks,
greg k-h
t; explicity at the callsite itself. Easier to read code.
>
> This patch should not introduce any change of behavior.
>
> Suggested-by: Dan Williams
> Signed-off-by: Vivek Goyal
> ---
Reviewed-by: Greg Kurz
> fs/dax.c | 23 +--
> 1 file ch
de
> according to usbtmc_read_bulk_cb() or
> usb_skeleton.c.
> @Dave: Do you have time? Otherwise I can do it.
> @Greg: Is it urgent?
No idea, but patches for known problems are always good to get completed
as soon as possible :)
thanks,
greg k-h
On Mon, Apr 19, 2021 at 09:25:19PM -0500, Frank Zago wrote:
> From: frank zago
>
> The 0x5512 USB PID is for the I2C/GPIO/SPI interfaces. UART is still
> present but only the TX and RX pins are available; DTS, DTR, ... are
> used for other things. Remove the PID, and let a I2C driver bind to
>
s simple enough, so I'd
simply drop it.
This is minor though and it shouldn't prevent this fix to go
forward.
Reviewed-by: Greg Kurz
> if (entry && !dax_is_conflict(entry))
> - dax_wake_entry(xas, entry, WAKE_NEXT);
> + dax_wake_entry(xas, en
comments.
Agreed, now dropped, thanks.
greg k-h
s done as a "research project" to see if they could mess with
kernel maintainers and slip in pointless changes to the kernel.
Not acceptable at all...
greg k-h
fer_release(fbinfo_crt);
>
> + kfree(info);
> return 0;
> }
>
> --
> 2.25.1
>
There is no function change here at all, please stop it with pointless
patches.
greg k-h
ll.
Stop submitting patches that you know are invalid. Your experiment is
not ethical, and not welcome or appreciated.
greg k-h
ssible to have happen.
Please stop submitting known-invalid patches. Your professor is playing
around with the review process in order to achieve a paper in some
strange and bizarre way.
This is not ok, it is wasting our time, and we will have to report this,
AGAIN, to your university...
greg k-h
On Mon, Apr 19, 2021 at 03:05:53PM +0200, Greg Kroah-Hartman wrote:
> From: Aditya Pakki
>
> [ Upstream commit 0c85a7e87465f2d4cbc768e245f4f45b2f299b05 ]
>
> In case of rs failure in rds_send_remove_from_sock(), the 'rm' resource
> is freed and later under spinlock, causing p
t
funding and support to FIX the bugs that those tools test. Right now,
the primary fixer of those findings are _INTERNS_ as that's all
companies are willing to fund to fix this type of thing.
And don't get me started on the inability for "executives" to fund other
parts of Linux that they rely on, because they want "other companies" to
do it instead. The tragedy-of-the-commons is a real threat to Linux,
and always has been...
thanks,
greg k-h
l FUSE file server is an untrusted piece of software
running in userspace, this is disabled by default. Only enable it
with virtiofs for now since virtiofsd is supposedly trusted by the
guest kernel.
Reported-by: Robert Krawitz
Signed-off-by: Greg Kurz
---
Can be tested using the following custom QEMU with F
From: Alexander Shiyan
[ Upstream commit e7a48c710defa0e0fef54d42b7d9e4ab596e2761 ]
When using the driver in I2S TDM mode, the fsl_esai_startup()
function rewrites the number of slots previously set by the
fsl_esai_set_dai_tdm_slot() function to 2.
To fix this, let's use the saved slot count
From: Alexander Aring
[ Upstream commit 080d1a57a94d93e70f84b7a360baa351388c574f ]
This patch stops dumping llsec devkeys for monitors which we don't support
yet. Otherwise we will access llsec mib which isn't initialized for
monitors.
Signed-off-by: Alexander Aring
Link:
ich checks if napi is disabled or not before calling napi_disable.
Fixes: bfc32f297337 ("ibmvnic: Move resource initialization to its own routine")
Suggested-by: Thomas Falcon
Signed-off-by: Lijun Pan
Signed-off-by: David S. Miller
Signed-off-by: Greg Kroah-Hartman
---
drivers/net
From: Heiner Kallweit
[ Upstream commit 21b5f672fb2eb1366dedc4ac9d32431146b378d3 ]
It turned out that on low performance systems the original change can
cause lower tx performance. On a N3450-based mini-PC tx performance
in iperf3 was reduced from 950Mbps to ~900Mbps. Therefore effectively
From: Heiner Kallweit
[ Upstream commit e0bbe7cbb3c5ff72d680993edf89db2391e80d5d ]
r8168b_0_hw_jumbo_enable() and r8168b_0_hw_jumbo_disable() both do the
same and just set PCI_EXP_DEVCTL_NOSNOOP_EN. We can simplify the code
by moving this setting for RTL8168B to rtl_hw_start_8168().
From: Heiner Kallweit
[ Upstream commit 9db0ac57bd3286fedcf43a86b29b847cea281cc7 ]
Merge enabling and disabling jumbo packets to one function to make
the code a little simpler.
Signed-off-by: Heiner Kallweit
Signed-off-by: David S. Miller
Signed-off-by: Sasha Levin
---
RS roots unaligned to block size")
Cc: sta...@vger.kernel.org
Signed-off-by: Jaegeuk Kim
Signed-off-by: Mike Snitzer
Signed-off-by: Greg Kroah-Hartman
---
drivers/md/dm-verity-fec.c | 11 ---
drivers/md/dm-verity-fec.h |1 +
2 files changed, 9 insertions(+), 3 deletions(-)
From: Andre Przywara
[ Upstream commit 3dd4ce4185df6798dcdcc3669bddb35899d7d5e1 ]
Commit 941432d00768 ("arm64: dts: allwinner: Drop non-removable from
SoPine/LTS SD card") enabled the card detect GPIO for the SOPine module,
along the way with the Pine64-LTS, which share the same base .dtsi.
From: Heiner Kallweit
[ Upstream commit 2df49d36549808a7357ad9f78b7a8e39516e7809 ]
The attempt to improve performance by changing the PCIe max read request
size was added in the vendor driver more than 10 years back and copied
to r8169 driver. In the vendor driver this has been removed long
From: Russell King
[ Upstream commit 30e3b4f256b4e366a61658c294f6a21b8626dda7 ]
Since commit 30fdfb929e82 ("PCI: Add a call to pci_assign_irq() in
pci_device_probe()"), the PCI code will call the IRQ mapping function
whenever a PCI driver is probed. If these are marked as __init, this
causes an
son Wang
Acked-by: Michael S. Tsirkin
Tested-by: Guenter Roeck
Signed-off-by: David S. Miller
Signed-off-by: Greg Kroah-Hartman
---
net/core/dev.c |3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
--- a/net/core/dev.c
+++ b/net/core/dev.c
@@ -5406,7 +5406,8 @@ static void skb_gro_reset_
t;)
Signed-off-by: Lijun Pan
Signed-off-by: David S. Miller
Signed-off-by: Greg Kroah-Hartman
---
drivers/net/ethernet/ibm/ibmvnic.c |5 -
1 file changed, 5 deletions(-)
--- a/drivers/net/ethernet/ibm/ibmvnic.c
+++ b/drivers/net/ethernet/ibm/ibmvnic.c
@@ -1088,11 +1088,6 @@
ewed-by: Andrew Lunn
Signed-off-by: David S. Miller
Signed-off-by: Greg Kroah-Hartman
---
drivers/net/dsa/mv88e6xxx/chip.c | 30 +-
drivers/net/phy/marvell.c| 29 ++---
include/linux/marvell_phy.h |5 +++--
3 files ch
et to call napi_schedule again at the end of the function
though napi_schedule will neglect the request if napi is already
scheduled.
Fixes: ed651a10875f ("ibmvnic: Updated reset handling")
Signed-off-by: Lijun Pan
Signed-off-by: David S. Miller
Signed-off-by: Greg Kroah-Hartman
---
are not permanently undefined.
Signed-off-by: Fredrik Strupe
Cc: sta...@vger.kernel.org
Fixes: c7edc9e326d5 ("ARM: add uprobes support")
Signed-off-by: Russell King
Signed-off-by: Greg Kroah-Hartman
---
arch/arm/probes/uprobes/core.c |4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
---
1 - 100 of 277221 matches
Mail list logo
