On Mon, 13 Feb 2017, Hans Verkuil wrote: > This is the v2 patch: > > https://patchwork.linuxtv.org/patch/32648/ Oh, ok, thanks! Guennadi > Hans > > On 02/13/2017 04:10 PM, Guennadi Liakhovetski wrote: > > Hi, > > > > According to the explanations below, "superseded" means, that either a > > newer version of the patch is available, or it's been included in a pull > > request. Since I don't see a newer version, I should assume, that it's > > been included in a pull request. However, I don't see one on linux-media > > either. How am I supposed to track such patch status changes? > > > > Thanks > > Guennadi > > > > ---------- Forwarded message ---------- > > Date: Mon, 13 Feb 2017 14:56:01 -0000 > > From: Patchwork <patchwork@xxxxxxxxxxx> > > To: g.liakhovetski@xxxxxx > > Subject: [linux-media] Patch notification: 1 patch updated > > > > Hello, > > > > The following patch (submitted by you) has been updated in patchwork: > > > > * linux-media: V4L: add Y12I, Y8I and Z16 pixel format documentation > > - http://patchwork.linuxtv.org/patch/32257/ > > - for: Linux Media kernel patches > > was: New > > now: Superseded > > > > This email is a notification only - you do not need to respond. > > > > - > > > > Patches submitted to linux-media@xxxxxxxxxxxxxxx have the following > > possible states: > > > > New: Patches not yet reviewed (typically new patches); > > > > Under review: When it is expected that someone is reviewing it (typically, > > the driver's author or maintainer). Unfortunately, patchwork > > doesn't have a field to indicate who is the driver maintainer. > > If in doubt about who is the driver maintainer please check the > > MAINTAINERS file or ask at the ML; > > > > Superseded: when the same patch is sent twice, or a new version of the > > same patch is sent, and the maintainer identified it, the first > > version is marked as such. It is also used when a patch was > > superseeded by a git pull request. > > > > Obsoleted: patch doesn't apply anymore, because the modified code doesn't > > exist anymore. > > > > Changes requested: when someone requests changes at the patch; > > > > Rejected: When the patch is wrong or doesn't apply. Most of the > > time, 'rejected' and 'changes requested' means the same thing > > for the developer: he'll need to re-work on the patch. > > > > RFC: patches marked as such and other patches that are also RFC, but the > > patch author was not nice enough to mark them as such. That includes: > > - patches sent by a driver's maintainer who send patches > > via git pull requests; > > - patches with a very active community (typically from developers > > working with embedded devices), where lots of versions are > > needed for the driver maintainer and/or the community to be > > happy with. > > > > Not Applicable: for patches that aren't meant to be applicable via > > the media-tree.git. > > > > Accepted: when some driver maintainer says that the patch will be applied > > via his tree, or when everything is ok and it got applied > > either at the main tree or via some other tree (fixes tree; > > some other maintainer's tree - when it belongs to other subsystems, > > etc); > > > > If you think any status change is a mistake, please send an email to the ML. > > > > - > > > > This is an automated mail sent by the patchwork system at > > patchwork.linuxtv.org. To stop receiving these notifications, edit > > your mail settings at: > > http://patchwork.linuxtv.org/mail/ > > >
