lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Tue, 8 Feb 2011 14:46:43 +0100
From:	Laurent Pinchart <laurent.pinchart@...asonboard.com>
To:	Sakari Ailus <sakari.ailus@...well.research.nokia.com>
Cc:	linux-media@...r.kernel.org, linux-kernel@...r.kernel.org,
	alsa-devel@...a-project.org, broonie@...nsource.wolfsonmicro.com,
	clemens@...isch.de
Subject: Re: [PATCH v8 03/12] media: Entities, pads and links

Hi Sakari,

On Friday 28 January 2011 11:53:39 Sakari Ailus wrote:
> Hi Laurent,
> 
> Thanks for the patches!
> 
> I've got one comment that I should have made long time ago... Pads are
> inputs or outputs... or: are they sinks or sources? I recall that it was
> agreed on some occasion that sink and source are much less ambiguous and
> they should be used instead.
> 
> So we'd have MEDIA_PAD_FL_{SINK,SOURCE}, for example. Currently the
> source and documentation is using input/output and source/sink
> interchangeably. I think sink and source should be used all the time.
> 
> What do you think?

I think it makes sense. Hans ?

-- 
Regards,

Laurent Pinchart
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists