All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Mark Brown <broonie@kernel.org>
Cc: Cezary Rojewski <cezary.rojewski@intel.com>,
	Kai Vehmanen <kai.vehmanen@linux.intel.com>,
	Bard Liao <yung-chuan.liao@linux.intel.com>,
	linux-kernel@vger.kernel.org, Takashi Iwai <tiwai@suse.com>,
	alsa-devel@alsa-project.org,
	Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>,
	Liam Girdwood <liam.r.girdwood@linux.intel.com>,
	Ranjani Sridharan <ranjani.sridharan@linux.intel.com>,
	Peter Ujfalusi <peter.ujfalusi@linux.intel.com>
Subject: Re: [PATCH v1 1/5] ASoC: Intel: bytcht_cx2072x: Replace open coded acpi_dev_put()
Date: Wed, 4 Jan 2023 20:55:31 +0200	[thread overview]
Message-ID: <Y7XLo8febtiSLGAD@smile.fi.intel.com> (raw)
In-Reply-To: <Y7W0VOJKlMtaIp13@sirena.org.uk>

On Wed, Jan 04, 2023 at 05:16:04PM +0000, Mark Brown wrote:
> On Wed, Jan 04, 2023 at 06:48:11PM +0200, Andy Shevchenko wrote:
> > On Wed, Jan 04, 2023 at 04:42:28PM +0000, Mark Brown wrote:
> 
> > > According to b4 you've only acked the first patch here because Andy
> > > doesn't send cover letters :/
> 
> > Is b4 capable to spread tags from cover letter to the whole series?
> > (Sorry, I'm a bit outdated with all Swiss-knife possibilities that
> >  b4 provides)
> 
> Yes, it does that.

Oh, cool to know! So it makes a lot of sense to create the cover letters
even for straightforward independent changes that are united into the
series for the easy handling.

Thank you!

P.S. Tell me if I need to resend with tags applied this time?

-- 
With Best Regards,
Andy Shevchenko



WARNING: multiple messages have this Message-ID (diff)
From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Mark Brown <broonie@kernel.org>
Cc: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>,
	alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org,
	Cezary Rojewski <cezary.rojewski@intel.com>,
	Liam Girdwood <liam.r.girdwood@linux.intel.com>,
	Peter Ujfalusi <peter.ujfalusi@linux.intel.com>,
	Bard Liao <yung-chuan.liao@linux.intel.com>,
	Ranjani Sridharan <ranjani.sridharan@linux.intel.com>,
	Kai Vehmanen <kai.vehmanen@linux.intel.com>,
	Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>
Subject: Re: [PATCH v1 1/5] ASoC: Intel: bytcht_cx2072x: Replace open coded acpi_dev_put()
Date: Wed, 4 Jan 2023 20:55:31 +0200	[thread overview]
Message-ID: <Y7XLo8febtiSLGAD@smile.fi.intel.com> (raw)
In-Reply-To: <Y7W0VOJKlMtaIp13@sirena.org.uk>

On Wed, Jan 04, 2023 at 05:16:04PM +0000, Mark Brown wrote:
> On Wed, Jan 04, 2023 at 06:48:11PM +0200, Andy Shevchenko wrote:
> > On Wed, Jan 04, 2023 at 04:42:28PM +0000, Mark Brown wrote:
> 
> > > According to b4 you've only acked the first patch here because Andy
> > > doesn't send cover letters :/
> 
> > Is b4 capable to spread tags from cover letter to the whole series?
> > (Sorry, I'm a bit outdated with all Swiss-knife possibilities that
> >  b4 provides)
> 
> Yes, it does that.

Oh, cool to know! So it makes a lot of sense to create the cover letters
even for straightforward independent changes that are united into the
series for the easy handling.

Thank you!

P.S. Tell me if I need to resend with tags applied this time?

-- 
With Best Regards,
Andy Shevchenko



  reply	other threads:[~2023-01-04 18:56 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-02 20:30 [PATCH v1 1/5] ASoC: Intel: bytcht_cx2072x: Replace open coded acpi_dev_put() Andy Shevchenko
2023-01-02 20:30 ` Andy Shevchenko
2023-01-02 20:30 ` [PATCH v1 2/5] ASoC: Intel: bytcht_da7213: " Andy Shevchenko
2023-01-02 20:30   ` Andy Shevchenko
2023-01-02 20:30 ` [PATCH v1 3/5] ASoC: Intel: cht_bsw_rt5645: " Andy Shevchenko
2023-01-02 20:30   ` Andy Shevchenko
2023-01-02 20:30 ` [PATCH v1 4/5] ASoC: Intel: cht_bsw_rt5672: " Andy Shevchenko
2023-01-02 20:30   ` Andy Shevchenko
2023-01-02 20:30 ` [PATCH v1 5/5] ASoC: Intel: sof-wm8804: " Andy Shevchenko
2023-01-02 20:30   ` Andy Shevchenko
2023-01-03 15:08 ` [PATCH v1 1/5] ASoC: Intel: bytcht_cx2072x: " Pierre-Louis Bossart
2023-01-03 15:08   ` Pierre-Louis Bossart
2023-01-04 10:29   ` Andy Shevchenko
2023-01-04 10:29     ` Andy Shevchenko
2023-01-04 14:15     ` Pierre-Louis Bossart
2023-01-04 14:15       ` Pierre-Louis Bossart
2023-01-04 16:42       ` Mark Brown
2023-01-04 16:42         ` Mark Brown
2023-01-04 16:48         ` Andy Shevchenko
2023-01-04 16:48           ` Andy Shevchenko
2023-01-04 17:16           ` Mark Brown
2023-01-04 17:16             ` Mark Brown
2023-01-04 18:55             ` Andy Shevchenko [this message]
2023-01-04 18:55               ` Andy Shevchenko
2023-01-05 11:46               ` Mark Brown
2023-01-05 11:46                 ` Mark Brown
2023-01-04 16:45       ` Andy Shevchenko
2023-01-04 16:45         ` Andy Shevchenko
2023-01-09 10:55       ` Andy Shevchenko
2023-01-09 10:55         ` Andy Shevchenko
2023-01-06 17:04 ` Mark Brown
2023-01-06 17:04   ` 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=Y7XLo8febtiSLGAD@smile.fi.intel.com \
    --to=andriy.shevchenko@linux.intel.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --cc=cezary.rojewski@intel.com \
    --cc=kai.vehmanen@linux.intel.com \
    --cc=liam.r.girdwood@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peter.ujfalusi@linux.intel.com \
    --cc=pierre-louis.bossart@linux.intel.com \
    --cc=ranjani.sridharan@linux.intel.com \
    --cc=tiwai@suse.com \
    --cc=yung-chuan.liao@linux.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 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.