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] [day] [month] [year] [list]
Date:   Sat, 27 Feb 2021 08:50:56 +0100
From:   Takashi Iwai <>
To:     Anton Yakovlev <>
Cc:     "Michael S. Tsirkin" <>,
        <>, <>,
        Jaroslav Kysela <>,
        Takashi Iwai <>, <>
Subject: Re: [PATCH v5 6/9] ALSA: virtio: PCM substream operators

On Fri, 26 Feb 2021 21:19:58 +0100,
Anton Yakovlev wrote:
> On 25.02.2021 21:30, Takashi Iwai wrote:> On Thu, 25 Feb 2021 20:02:50
> +0100,
> > Michael S. Tsirkin wrote:
> >>
> [snip]
> >> If you want to merge it yourself instead, also please say so.
> >
> > I don't mind who take the patches, although it looks more fitting to
> > merge through sound git tree if judging from the changes put in
> > sound/* directory.
> Then should I update the MAINTAINERS and add Takashi instead of
> Michael, or should I put both of you there?

No need for that, I'm already named as the generic sound/* stuff
maintainer.  And, it's rather more about how the merge gets pushed up
to upstream.  In general, the stuff belonging to a subsystem goes via
the subsystem tree, e.g. Mark has been maintaining ASoC stuff in his 
tree while it gets merged sound.git tree to Linus.  Similarly, it's
fine if Michael wants to keep a sub-subsystem tree for virtio_snd,
too.  But keeping a dedicated git repo for a single driver isn't often

Of course, it's no strict rule, and I don't mind if anybody has a
strong reason to process in other ways, too.  Just let me know.



Powered by blists - more mailing lists