alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Vaishali Thakkar <vthakkar1994@gmail.com>
Cc: Takashi Iwai <tiwai@suse.de>, alsa-devel@alsa-project.org
Subject: Re: [PATCH] ASoC: wm5102: Use put_unaligned_be16
Date: Mon, 29 Dec 2014 16:57:34 +0000	[thread overview]
Message-ID: <20141229165734.GA17800@sirena.org.uk> (raw)
In-Reply-To: <CAK-LDb+KCWHz7A5im7cB=dQfCs8ioh2T+jsxk9PdAFHNSOuvzg@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 1628 bytes --]

On Mon, Dec 29, 2014 at 10:00:13PM +0530, Vaishali Thakkar wrote:
> On Mon, Dec 29, 2014 at 9:23 PM, Mark Brown <broonie@kernel.org> wrote:

> > You sent this on the 26th, two days later on the 28th you're demanding a
> > review and complaining that we've missed this with a top posted quote.
> > Even during a normal working period this would not be a reasnoable
> > demand (a couple of weeks is normally a good *lower* limit, people have
> > vacations and other things to do), and right now we're in the middle of
> > the time of year when people from western societies typically take
> > vacation.

> I am really very sorry for this. Actually I am a newbie. I mainly
> worked during opw-application period and there we used to work with
> staging directory only. This is my first time, I am working with other
> parts of kernel. So, I had kind of feeling that I might have done
> something wrong that's why I am not getting any comments. But I think
> its my fault. I may need to understand workflow of community properly
> and I apologizes for that.

Basically you should be allowing something measured in weeks to get a
response rather than days unless there's some ultra critical issue -
people might be busy, on vacation or whatever.  Different parts of the
kernel will have different working patterns and rules of thumb but in
general be patient, try to leave it for a few weeks before doing
anything unless you realise that there's some problem (eg, you forgot to
CC someone or you spot a mistake yourself in which case do a new version
fixing that mistake).  If it's just been a week or two people might just
be busy.

[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]

[-- Attachment #2: Type: text/plain, Size: 0 bytes --]



  reply	other threads:[~2014-12-29 16:57 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-26  4:44 [PATCH] ASoC: wm5102: Use put_unaligned_be16 Vaishali Thakkar
2014-12-28 11:05 ` Vaishali Thakkar
2014-12-29 15:53   ` Mark Brown
2014-12-29 16:30     ` Vaishali Thakkar
2014-12-29 16:57       ` Mark Brown [this message]
2014-12-29 17:19         ` Vaishali Thakkar
2015-01-07 10:01 ` Charles Keepax
2015-01-07 15:24   ` Vaishali Thakkar
2015-01-07 16:47     ` Charles Keepax
2015-01-07 17:45 ` Mark Brown
  -- strict thread matches above, loose matches on Subject: below --
2014-12-26  4:39 Vaishali Thakkar

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=20141229165734.GA17800@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=alsa-devel@alsa-project.org \
    --cc=tiwai@suse.de \
    --cc=vthakkar1994@gmail.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;
as well as URLs for NNTP newsgroup(s).