From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Patrik Sevallius <patrik.sevallius@enea.com>
Cc: alsa-devel@alsa-project.org, Frank Mandarino <fmandarino@endrelia.com>
Subject: Re: [PATCH] soc at91 minor bug fixes
Date: Thu, 8 May 2008 11:36:58 +0100 [thread overview]
Message-ID: <20080508103657.GB10313@rakim.wolfsonmicro.main> (raw)
In-Reply-To: <DC6F86A94046A64094043D44A3A708F7A8DFE1@sestoex02.enea.se>
On Thu, May 08, 2008 at 08:22:48AM +0200, Patrik Sevallius wrote:
> Found these two bugs while browsing through the code.
Thanks, I've committed this to the ASoC repository and pushed it back
out together with a line wrapping change required to make your patch
checkpatch-clean.
> Frank Mandarino was busy so he asked me to send these to this list.
Since Frank isn't passing on the patch directly this:
> Signed-off-by: Frank Mandarino <fmandarino@endrelia.com>
should be Acked-by rather than Signed-off-by (the signoffs should track
the path the patch took into the kernel).
prev parent reply other threads:[~2008-05-08 10:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-08 6:22 [PATCH] soc at91 minor bug fixes Patrik Sevallius
2008-05-08 10:36 ` Mark Brown [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=20080508103657.GB10313@rakim.wolfsonmicro.main \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=fmandarino@endrelia.com \
--cc=patrik.sevallius@enea.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