public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Rishabh Bhatnagar <rishabhb@codeaurora.org>
Cc: linux-remoteproc@vger.kernel.org, linux-kernel@vger.kernel.org,
	bjorn.andersson@linaro.org, tsoni@codeaurora.org,
	psodagud@codeaurora.org, sidgup@codeaurora.org
Subject: Re: [PATCH v3 0/3] Expose recovery/coredump configuration from sysfs
Date: Fri, 4 Sep 2020 08:46:43 +0100	[thread overview]
Message-ID: <20200904074643.GA26741@infradead.org> (raw)
In-Reply-To: <1599174226-2307-1-git-send-email-rishabhb@codeaurora.org>

On Thu, Sep 03, 2020 at 04:03:42PM -0700, Rishabh Bhatnagar wrote:
> >From Android R onwards Google has restricted access to debugfs in user
> and user-debug builds. This restricts access to most of the features
> exposed through debugfs. This patch series removes the recovery/coredump
> entries from debugfs and adds a configurable option to expose these
> interfaces from sysfs. 

so please fix android instead of messing up the upstream kernel.

      parent reply	other threads:[~2020-09-04  7:46 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-03 23:03 [PATCH v3 0/3] Expose recovery/coredump configuration from sysfs Rishabh Bhatnagar
2020-09-03 23:03 ` [PATCH v3 1/3] remoteproc: Expose remoteproc configuration through sysfs Rishabh Bhatnagar
2020-09-04  0:04   ` Bjorn Andersson
2020-09-04 22:07     ` Mathieu Poirier
2020-09-03 23:03 ` [PATCH v3 2/3] remoteproc: Add coredump configuration to sysfs Rishabh Bhatnagar
2020-09-03 23:03 ` [PATCH v3 3/3] remoteproc: Add recovery " Rishabh Bhatnagar
2020-09-04  7:46 ` Christoph Hellwig [this message]

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=20200904074643.GA26741@infradead.org \
    --to=hch@infradead.org \
    --cc=bjorn.andersson@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-remoteproc@vger.kernel.org \
    --cc=psodagud@codeaurora.org \
    --cc=rishabhb@codeaurora.org \
    --cc=sidgup@codeaurora.org \
    --cc=tsoni@codeaurora.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