mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Abhinav Kumar <quic_abhinavk@quicinc.com>, linux-kernel@vger.kernel.org
Cc: rafael@kernel.org, linux-arm-msm@vger.kernel.org,
	dri-devel@lists.freedesktop.org, swboyd@chromium.org,
	khsieh@codeaurora.org, nganji@codeaurora.org,
	seanpaul@chromium.org, gregkh@linuxfoundation.org,
	dmitry.baryshkov@linaro.org, aravindh@codeaurora.org,
	freedreno@lists.freedesktop.org
Subject: Re: [PATCH] devcoredump: increase the device delete timeout to 10 mins
Date: Wed, 09 Feb 2022 08:50:19 +0100	[thread overview]
Message-ID: <2d71a9c0d2cd0b0c82a627b0585040c81a4523fa.camel@sipsolutions.net> (raw)
In-Reply-To: <b60d30cf-e435-49c4-a251-b910bc2e94ae@quicinc.com>

On Tue, 2022-02-08 at 17:55 -0800, Abhinav Kumar wrote:
> 
> Are you suggesting something like below?
> 
> diff --git a/fs/sysfs/file.c b/fs/sysfs/file.c
> index 42dcf96..14203d0 100644
> --- a/fs/sysfs/file.c
> 

No, for sure not, but I guess from the looks of this patch there's no
way to do something like that for just an individual attribute...

Oh well.

johannes

  reply	other threads:[~2022-02-09  7:50 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-08 19:44 Abhinav Kumar
2022-02-08 20:35 ` Johannes Berg
2022-02-08 21:04   ` Abhinav Kumar
2022-02-08 21:12     ` Johannes Berg
2022-02-08 21:40       ` Abhinav Kumar
2022-02-08 21:54         ` Johannes Berg
2022-02-09  1:55           ` Abhinav Kumar
2022-02-09  7:50             ` Johannes Berg [this message]
2022-02-09 16:29               ` Abhinav Kumar
2022-02-11 11:09             ` Greg KH
2022-02-11 11:09 ` Greg KH
2022-02-11 18:59   ` Abhinav Kumar
2022-02-12  7:04     ` Greg KH
2022-02-12  7:52       ` Abhinav Kumar
2022-02-12  8:24         ` Johannes Berg
2022-02-12  8:35           ` Abhinav Kumar
2022-02-28 21:38             ` Abhinav Kumar
2022-03-01  6:48               ` David Laight
2022-03-01 17:45                 ` Rob Clark
2022-03-11 11:53                   ` Johannes Berg
2022-02-12  8:29         ` Greg KH
2022-02-12  8:33           ` Abhinav Kumar

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=2d71a9c0d2cd0b0c82a627b0585040c81a4523fa.camel@sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=aravindh@codeaurora.org \
    --cc=dmitry.baryshkov@linaro.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=freedreno@lists.freedesktop.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=khsieh@codeaurora.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nganji@codeaurora.org \
    --cc=quic_abhinavk@quicinc.com \
    --cc=rafael@kernel.org \
    --cc=seanpaul@chromium.org \
    --cc=swboyd@chromium.org \
    /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®