All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Dan Murphy <dmurphy@ti.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	Liam Girdwood <lgirdwood@gmail.com>,
	Linux Next Mailing List <linux-next@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: Fixes tag needs some work in the sound-asoc-fixes tree
Date: Thu, 14 May 2020 11:04:46 +0100	[thread overview]
Message-ID: <20200514100446.GA5127@sirena.org.uk> (raw)
In-Reply-To: <f828c953-07b2-6a6b-881a-bf10f20a719d@ti.com>

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

On Wed, May 13, 2020 at 04:20:32PM -0500, Dan Murphy wrote:

> Did you want me to re-submit the patch with the corrected commit or are you
> going to update it?

No, just leave it - I don't rebase my trees.  Please try to avoid issues
like this in future :/

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

  reply	other threads:[~2020-05-14 10:04 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-13 21:12 linux-next: Fixes tag needs some work in the sound-asoc-fixes tree Stephen Rothwell
2020-05-13 21:20 ` Dan Murphy
2020-05-14 10:04   ` Mark Brown [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-10-31 21:06 Stephen Rothwell
2021-12-16 13:00 Stephen Rothwell
2021-11-14  7:23 Stephen Rothwell
2021-06-01 22:00 Stephen Rothwell
2020-04-28 21:59 Stephen Rothwell
2020-04-14 22:00 Stephen Rothwell
2020-03-12 20:39 Stephen Rothwell
2020-03-01  5:38 Stephen Rothwell
2020-02-19  3:14 Stephen Rothwell
2020-01-19  1:13 Stephen Rothwell
2019-10-01 22:29 Stephen Rothwell
2019-10-02  7:55 ` Kai Vehmanen
2019-06-10 18:41 Stephen Rothwell
2019-06-06 22:01 Stephen Rothwell
2019-05-13 15:00 Stephen Rothwell
2019-04-10 21:00 Stephen Rothwell
2019-02-26 20:42 Stephen Rothwell
2019-02-07 20:31 Stephen Rothwell
2019-02-06 20:05 Stephen Rothwell

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=20200514100446.GA5127@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=dmurphy@ti.com \
    --cc=lgirdwood@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    /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.