public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Hans Verkuil <hverkuil@xs4all.nl>
To: Antti Palosaari <crope@iki.fi>, linux-media@vger.kernel.org
Subject: Re: [ATTN 0/9] SDR transmitter API
Date: Fri, 05 Jun 2015 12:30:14 +0200	[thread overview]
Message-ID: <55717A36.7010808@xs4all.nl> (raw)
In-Reply-To: <55717910.7050002@iki.fi>

On 06/05/2015 12:25 PM, Antti Palosaari wrote:
> On 06/05/2015 12:50 PM, Hans Verkuil wrote:
>> Hi Antti,
>>
>> FYI: don't use ATTN as prefix: patchwork doesn't pick that up as a patch,
>> and if it doesn't appear there, then it is likely to be forgotten.
>>
>> Can you repost it with the correct prefix? It's so much easier to process
>> for me if it ends up in patchwork...
> 
> Which is correct prefix?

Just [PATCH] is enough.

> 
> Earlier I used PATCH RFC, but then I saw that ATTN:
> [ANN] Report on the San Jose V4L/DVB mini-summit
> http://www.spinics.net/lists/linux-media/msg76281.html
> 
> - Add 'ATTN' inside pull request subject line tp indicate that Mauro's 
> (or some other maintainer's) attention is required. Should be limited to 
> api changes, dependencies.
> 
> OK, it speaks only pull request, but that was patchset having API changes...

ATTN is only for urgent pull requests for the current rc kernel, it doesn't
apply to patches.

[PATCH RFC] means that it is not yet ready to be merged, but just [PATCH] indicates
that it should be OK to merge (at least according to the submitter!).

Regards,

	Hans

      reply	other threads:[~2015-06-05 10:30 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-26 17:08 [ATTN 0/9] SDR transmitter API Antti Palosaari
2015-05-26 17:08 ` [ATTN 1/9] v4l2: rename V4L2_TUNER_ADC to V4L2_TUNER_SDR Antti Palosaari
2015-05-26 17:08 ` [ATTN 2/9] v4l2: add RF gain control Antti Palosaari
2015-05-26 17:08 ` [ATTN 3/9] DocBook: document tuner " Antti Palosaari
2015-05-26 17:08 ` [ATTN 4/9] v4l2: add support for SDR transmitter Antti Palosaari
2015-05-26 17:08 ` [ATTN 5/9] DocBook: document " Antti Palosaari
2015-05-26 17:08 ` [ATTN 6/9] hackrf: add control for RF amplifier Antti Palosaari
2015-05-26 17:08 ` [ATTN 7/9] hackrf: switch to single function which configures everything Antti Palosaari
2015-05-26 17:08 ` [ATTN 8/9] hackrf: add support for transmitter Antti Palosaari
2015-05-26 17:08 ` [ATTN 9/9] hackrf: do not set human readable name for formats Antti Palosaari
2015-06-05  9:50 ` [ATTN 0/9] SDR transmitter API Hans Verkuil
2015-06-05 10:25   ` Antti Palosaari
2015-06-05 10:30     ` Hans Verkuil [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=55717A36.7010808@xs4all.nl \
    --to=hverkuil@xs4all.nl \
    --cc=crope@iki.fi \
    --cc=linux-media@vger.kernel.org \
    /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