From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Mark Brown <broonie@kernel.org>,
Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Cc: alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org,
Oder Chiou <oder_chiou@realtek.com>,
Liam Girdwood <lgirdwood@gmail.com>,
Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>
Subject: Re: [PATCH v2 0/4] ASoC: rt5677: Refactor GPIO and use device_get_match_data()
Date: Wed, 12 Jul 2023 18:31:29 +0300 [thread overview]
Message-ID: <ZK7HUTyKB6hoaBtV@smile.fi.intel.com> (raw)
In-Reply-To: <d5cac1ef-1d44-4ab7-a933-b381108b1eaa@sirena.org.uk>
+Cc: Konstantin.
Konstantin, seems b4 doesn't handle long Subject lines for merge commits
(PR mode).
On Wed, Jul 12, 2023 at 04:23:11PM +0100, Mark Brown wrote:
> On Wed, Jul 12, 2023 at 04:56:51PM +0300, Andy Shevchenko wrote:
>
> > JFYI: You might need to amend your scripts (?) as in the merge commit
> > the Subject is cut (I believe that your scripts doesn't handle
> > RFC2822 long lines in the email headers).
>
> Report that to Konstantin, this is just b4.
--
With Best Regards,
Andy Shevchenko
prev parent reply other threads:[~2023-07-12 15:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-30 17:21 [PATCH v2 0/4] ASoC: rt5677: Refactor GPIO and use device_get_match_data() Andy Shevchenko
2023-06-30 17:21 ` [PATCH v2 1/4] ASoC: rt5677: Refactor GPIO support code Andy Shevchenko
2023-06-30 17:21 ` [PATCH v2 2/4] ASoC: rt5677: Use agnostic irq_domain_create_linear() Andy Shevchenko
2023-06-30 17:21 ` [PATCH v2 3/4] ASoC: rt5677: Use device_get_match_data() Andy Shevchenko
2023-06-30 17:21 ` [PATCH v2 4/4] ASoC: rt5677: Sort headers alphabetically Andy Shevchenko
2023-07-12 11:47 ` [PATCH v2 0/4] ASoC: rt5677: Refactor GPIO and use device_get_match_data() Mark Brown
2023-07-12 13:56 ` Andy Shevchenko
2023-07-12 15:23 ` Mark Brown
2023-07-12 15:31 ` Andy Shevchenko [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=ZK7HUTyKB6hoaBtV@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=konstantin@linuxfoundation.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=oder_chiou@realtek.com \
--cc=perex@perex.cz \
--cc=tiwai@suse.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox