From: Johannes Berg <johannes@sipsolutions.net>
To: "José Roberto de Souza" <jose.souza@intel.com>,
linux-kernel@vger.kernel.org, intel-xe@lists.freedesktop.org,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>
Cc: Rodrigo Vivi <rodrigo.vivi@intel.com>,
Mukesh Ojha <quic_mojha@quicinc.com>,
Jonathan Cavitt <jonathan.cavitt@intel.com>
Subject: Re: [PATCH v6 1/2] devcoredump: Add dev_coredumpm_timeout()
Date: Wed, 12 Jun 2024 14:02:37 +0200 [thread overview]
Message-ID: <49c2fbdc91d128c5249d50d016d97c8e5162f7b7.camel@sipsolutions.net> (raw)
In-Reply-To: <20240611174716.72660-1-jose.souza@intel.com>
On Tue, 2024-06-11 at 10:47 -0700, José Roberto de Souza wrote:
> Add function to set a custom coredump timeout.
>
> For Xe driver usage, current 5 minutes timeout may be too short for
> users to search and understand what needs to be done to capture
> coredump to report bugs.
>
> We have plans to automate(distribute a udev script) it but at the end
> will be up to distros and users to pack it so having a option to
> increase the timeout is a safer option.
>
> v2:
> - replace dev_coredump_timeout_set() by dev_coredumpm_timeout() (Mukesh)
>
> v3:
> - make dev_coredumpm() static inline (Johannes)
>
> v5:
> - rename DEVCOREDUMP_TIMEOUT -> DEVCD_TIMEOUT to avoid redefinition
> in include/net/bluetooth/coredump.h
>
> v6:
> - fix definition of dev_coredumpm_timeout() when CONFIG_DEV_COREDUMP
> is disabled
Got to v6, heh.
I still don't think this is _right_, but I guess I'm OK with giving you
rope to hang yourself ;-)
Acked-by: Johannes Berg <johannes@sipsolutions.net>
Seems like you really should've CC'ed Greg though since these things
usually went through his tree, so if you want to take them through yours
he really should be at least aware ...
johannes
next prev parent reply other threads:[~2024-06-12 12:41 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-11 17:47 [PATCH v6 1/2] devcoredump: Add dev_coredumpm_timeout() José Roberto de Souza
2024-06-11 17:47 ` [PATCH v6 2/2] drm/xe: Increase devcoredump timeout José Roberto de Souza
2024-06-11 18:39 ` ✓ CI.Patch_applied: success for series starting with [v6,1/2] devcoredump: Add dev_coredumpm_timeout() Patchwork
2024-06-11 18:39 ` ✓ CI.checkpatch: " Patchwork
2024-06-11 18:40 ` ✓ CI.KUnit: " Patchwork
2024-06-11 18:52 ` ✓ CI.Build: " Patchwork
2024-06-11 18:54 ` ✗ CI.Hooks: failure " Patchwork
2024-06-11 18:55 ` ✓ CI.checksparse: success " Patchwork
2024-06-11 19:17 ` ✓ CI.BAT: " Patchwork
2024-06-11 23:28 ` ✗ CI.FULL: failure " Patchwork
2024-06-12 12:02 ` Johannes Berg [this message]
2024-06-12 14:54 ` [PATCH v6 1/2] " Rodrigo Vivi
2024-06-12 15:10 ` Greg Kroah-Hartman
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=49c2fbdc91d128c5249d50d016d97c8e5162f7b7.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=gregkh@linuxfoundation.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=jonathan.cavitt@intel.com \
--cc=jose.souza@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=quic_mojha@quicinc.com \
--cc=rodrigo.vivi@intel.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