From: Jani Nikula <jani.nikula@linux.intel.com>
To: "Anand, Jerome" <jerome.anand@intel.com>,
"Ville Syrjälä" <ville.syrjala@linux.intel.com>
Cc: "tiwai@suse.de" <tiwai@suse.de>,
"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
"broonie@kernel.org" <broonie@kernel.org>,
"Ughreja, Rakesh A" <rakesh.a.ughreja@intel.com>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>
Subject: Re: [RFC PATCH v3 1/7] drm/i915: setup bridge for HDMI LPE audio driver
Date: Mon, 28 Nov 2016 10:06:48 +0200 [thread overview]
Message-ID: <871sxw2fl3.fsf@intel.com> (raw)
In-Reply-To: <F6867404AABACB4D8EC371BF802A4B7C149269C2@fmsmsx101.amr.corp.intel.com>
On Mon, 28 Nov 2016, "Anand, Jerome" <jerome.anand@intel.com> wrote:
> Last time , it took close to 10 days when my patches were reflected on
> the gfx mailing list. Not sure what is the problem ?? Let me try
> sending it again ??
I guess the last time they only ever showed up because Ville bounced
them to the list after I'd wondered where the patches were...
Clearly the patches go through to people directly, at least Ville, and
your replies on the list go through, but there's got to be something
going on with how you send patches to the lists. (I'd suspect
freedesktop.org, but the patches weren't on alsa-devel archive either.)
You already seem to be using 'git send-email'. I don't know what to
suggest next, except to maybe try to send a test mail to the list using
'git send-email' and see if it goes through.
BR,
Jani.
--
Jani Nikula, Intel Open Source Technology Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2016-11-28 8:06 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20161124235548.16440-1-jerome.anand@intel.com>
[not found] ` <20161124235548.16440-2-jerome.anand@intel.com>
2016-11-24 13:31 ` [RFC PATCH v3 1/7] drm/i915: setup bridge for HDMI LPE audio driver Ville Syrjälä
2016-11-25 5:42 ` Anand, Jerome
2016-11-25 10:18 ` Ville Syrjälä
2016-11-25 10:52 ` Jani Nikula
2016-11-28 1:50 ` Anand, Jerome
2016-11-28 8:06 ` Jani Nikula [this message]
2016-11-27 18:20 ` [alsa-devel] " Pierre-Louis Bossart
2016-11-28 13:43 ` Ville Syrjälä
[not found] ` <20161124235548.16440-3-jerome.anand@intel.com>
2016-11-24 13:32 ` [RFC PATCH v3 2/7] drm/i915: Add support for audio driver notifications Ville Syrjälä
2016-11-25 5:51 ` Anand, Jerome
2016-11-28 14:00 ` Ville Syrjälä
2016-11-28 16:50 ` Anand, Jerome
2016-11-28 17:01 ` Ville Syrjälä
2016-11-28 19:13 ` Pierre-Louis Bossart
2016-11-28 19:30 ` Ville Syrjälä
2016-11-28 21:56 ` Pierre-Louis Bossart
2016-11-29 8:27 ` Takashi Iwai
2016-11-29 16:22 ` Anand, Jerome
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=871sxw2fl3.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jerome.anand@intel.com \
--cc=rakesh.a.ughreja@intel.com \
--cc=tiwai@suse.de \
--cc=ville.syrjala@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.