All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dan Carpenter <error27@gmail.com>
To: Hans Verkuil <hverkuil@xs4all.nl>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Deepak R Varma <drv@mailo.com>,
	Mauro Carvalho Chehab <mchehab@kernel.org>,
	Kevin Hilman <khilman@baylibre.com>,
	Jerome Brunet <jbrunet@baylibre.com>,
	Martin Blumenstingl <martin.blumenstingl@googlemail.com>,
	linux-media@vger.kernel.org, linux-amlogic@lists.infradead.org,
	linux-staging@lists.linux.dev,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org,
	Neil Armstrong <neil.armstrong@linaro.org>
Subject: Re: patches for staging:media drivers
Date: Tue, 8 Nov 2022 12:46:25 +0300	[thread overview]
Message-ID: <Y2olcaNp3xkRRK7j@kadam> (raw)
In-Reply-To: <bf7dc5f6-acf3-73f0-b73b-d5707152190b@xs4all.nl>

On Tue, Nov 08, 2022 at 10:35:54AM +0100, Hans Verkuil wrote:
> 
> I don't mind taking patches for media staging drivers as long as:
> 
> 1) they are not for atomisp, and
> 2) they are not for deprecated drivers (drivers/staging/media/deprecated/)
> 

This is unrelated but I somehow misread an email and thought we were
going to create a drivers/deprecated/ directory.  I still think that's a
good idea for future deprecated drivers.  We normally put them in
staging/ but it's not really the ideal place for them.

regards,
dan carpenter

_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic

WARNING: multiple messages have this Message-ID (diff)
From: Dan Carpenter <error27@gmail.com>
To: Hans Verkuil <hverkuil@xs4all.nl>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Deepak R Varma <drv@mailo.com>,
	Mauro Carvalho Chehab <mchehab@kernel.org>,
	Kevin Hilman <khilman@baylibre.com>,
	Jerome Brunet <jbrunet@baylibre.com>,
	Martin Blumenstingl <martin.blumenstingl@googlemail.com>,
	linux-media@vger.kernel.org, linux-amlogic@lists.infradead.org,
	linux-staging@lists.linux.dev,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org,
	Neil Armstrong <neil.armstrong@linaro.org>
Subject: Re: patches for staging:media drivers
Date: Tue, 8 Nov 2022 12:46:25 +0300	[thread overview]
Message-ID: <Y2olcaNp3xkRRK7j@kadam> (raw)
In-Reply-To: <bf7dc5f6-acf3-73f0-b73b-d5707152190b@xs4all.nl>

On Tue, Nov 08, 2022 at 10:35:54AM +0100, Hans Verkuil wrote:
> 
> I don't mind taking patches for media staging drivers as long as:
> 
> 1) they are not for atomisp, and
> 2) they are not for deprecated drivers (drivers/staging/media/deprecated/)
> 

This is unrelated but I somehow misread an email and thought we were
going to create a drivers/deprecated/ directory.  I still think that's a
good idea for future deprecated drivers.  We normally put them in
staging/ but it's not really the ideal place for them.

regards,
dan carpenter

WARNING: multiple messages have this Message-ID (diff)
From: Dan Carpenter <error27@gmail.com>
To: Hans Verkuil <hverkuil@xs4all.nl>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Deepak R Varma <drv@mailo.com>,
	Mauro Carvalho Chehab <mchehab@kernel.org>,
	Kevin Hilman <khilman@baylibre.com>,
	Jerome Brunet <jbrunet@baylibre.com>,
	Martin Blumenstingl <martin.blumenstingl@googlemail.com>,
	linux-media@vger.kernel.org, linux-amlogic@lists.infradead.org,
	linux-staging@lists.linux.dev,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org,
	Neil Armstrong <neil.armstrong@linaro.org>
Subject: Re: patches for staging:media drivers
Date: Tue, 8 Nov 2022 12:46:25 +0300	[thread overview]
Message-ID: <Y2olcaNp3xkRRK7j@kadam> (raw)
In-Reply-To: <bf7dc5f6-acf3-73f0-b73b-d5707152190b@xs4all.nl>

On Tue, Nov 08, 2022 at 10:35:54AM +0100, Hans Verkuil wrote:
> 
> I don't mind taking patches for media staging drivers as long as:
> 
> 1) they are not for atomisp, and
> 2) they are not for deprecated drivers (drivers/staging/media/deprecated/)
> 

This is unrelated but I somehow misread an email and thought we were
going to create a drivers/deprecated/ directory.  I still think that's a
good idea for future deprecated drivers.  We normally put them in
staging/ but it's not really the ideal place for them.

regards,
dan carpenter

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2022-11-08  9:46 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-06 10:52 patches for staging:media drivers Deepak R Varma
2022-11-06 10:52 ` Deepak R Varma
2022-11-06 10:52 ` Deepak R Varma
2022-11-07 17:29 ` Neil Armstrong
2022-11-07 17:29   ` Neil Armstrong
2022-11-07 17:29   ` Neil Armstrong
2022-11-07 18:57   ` Deepak R Varma
2022-11-07 18:57     ` Deepak R Varma
2022-11-07 18:57     ` Deepak R Varma
2022-11-08  8:10   ` Dan Carpenter
2022-11-08  8:10     ` Dan Carpenter
2022-11-08  8:10     ` Dan Carpenter
2022-11-08  9:35     ` Hans Verkuil
2022-11-08  9:35       ` Hans Verkuil
2022-11-08  9:35       ` Hans Verkuil
2022-11-08  9:46       ` Dan Carpenter [this message]
2022-11-08  9:46         ` Dan Carpenter
2022-11-08  9:46         ` Dan Carpenter
2022-11-08 20:27     ` Andrew Lunn
2022-11-08 20:27       ` Andrew Lunn
2022-11-08 20:27       ` Andrew Lunn
2022-11-09  6:40       ` Deepak R Varma
2022-11-09  6:40         ` Deepak R Varma
2022-11-09  6:40         ` Deepak R Varma
2022-11-09 13:49         ` Andrew Lunn
2022-11-09 13:49           ` Andrew Lunn
2022-11-09 13:49           ` Andrew Lunn
2022-11-11 17:11           ` Deepak R Varma
2022-11-11 17:11             ` Deepak R Varma
2022-11-11 17:11             ` Deepak R Varma

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=Y2olcaNp3xkRRK7j@kadam \
    --to=error27@gmail.com \
    --cc=drv@mailo.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=hverkuil@xs4all.nl \
    --cc=jbrunet@baylibre.com \
    --cc=khilman@baylibre.com \
    --cc=linux-amlogic@lists.infradead.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=linux-staging@lists.linux.dev \
    --cc=martin.blumenstingl@googlemail.com \
    --cc=mchehab@kernel.org \
    --cc=neil.armstrong@linaro.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.