All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Ricardo Ribalda <ribalda@chromium.org>
Cc: Support Opensource <support.opensource@diasemi.com>,
	Liam Girdwood <lgirdwood@gmail.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1 1/1] regulator: da9211: Use irq handler when ready
Date: Thu, 24 Nov 2022 17:41:31 +0000	[thread overview]
Message-ID: <Y3+sy9hJ4U3CwWzb@sirena.org.uk> (raw)
In-Reply-To: <CANiDSCuMA3N-spbKQUZJywKMhxZyd-YB0bYSEeC9reQJOSi7mw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 716 bytes --]

On Thu, Nov 24, 2022 at 06:35:42PM +0100, Ricardo Ribalda wrote:

> On Thu, 24 Nov 2022 at 17:54, Mark Brown <broonie@kernel.org> wrote:
> > On Thu, Nov 24, 2022 at 05:45:31PM +0100, Ricardo Ribalda wrote:

> > Please think hard before including complete backtraces in upstream
> > reports, they are very large and contain almost no useful information
> > relative to their size so often obscure the relevant content in your
> > message. If part of the backtrace is usefully illustrative (it often is
> > for search engines if nothing else) then it's usually better to pull out
> > the relevant sections.

> Do you want that I post a v2 of the patch?

It's fine, just please think about this for future submissions.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2022-11-24 17:41 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-24 16:45 [PATCH v1 0/1] regulator: da9211: Fix crash when irqs are pre-enabled Ricardo Ribalda
2022-11-24 16:45 ` [PATCH v1 1/1] regulator: da9211: Use irq handler when ready Ricardo Ribalda
2022-11-24 16:53   ` Mark Brown
2022-11-24 17:35     ` Ricardo Ribalda
2022-11-24 17:41       ` Mark Brown [this message]
2022-11-27 20:55   ` DLG Adam Ward
2022-11-24 16:52 ` [PATCH v1 0/1] regulator: da9211: Fix crash when irqs are pre-enabled Mark Brown
2022-11-24 17:33   ` Ricardo Ribalda
2022-11-29 16:46 ` Mark Brown

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=Y3+sy9hJ4U3CwWzb@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=lgirdwood@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ribalda@chromium.org \
    --cc=support.opensource@diasemi.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.