All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: LakshmiPraveen.Kopparthi@microchip.com
Cc: linux-serial@vger.kernel.org, Woojung.Huh@microchip.com,
	Sundararaman.H@microchip.com,
	Kumaravel.Thiagarajan@microchip.com,
	GaneshKumar.Gurumurthy@microchip.com,
	Muthukumar.Veeramani@microchip.com
Subject: Re: TIOCSERCONFIG ioctl does not respect UPF_FIXED_TYPE flag
Date: Fri, 11 Dec 2020 09:42:22 +0100	[thread overview]
Message-ID: <X9Mw7lNRo+rEpyFP@kroah.com> (raw)
In-Reply-To: <DM6PR11MB2586CF444FFBF203D0709A5093CA0@DM6PR11MB2586.namprd11.prod.outlook.com>

On Fri, Dec 11, 2020 at 08:21:23AM +0000, LakshmiPraveen.Kopparthi@microchip.com wrote:
> Hi,

Hi,

Please don't send email in html format, the mailing lists reject it :(

>     We are working on a patch to add the serial support for our device. In that process, it appears TIOCSERCONFIG ioctl does not respect the UPF_FIXED_TYPE flag.  uart_do_autoconfig gets called which passes UART_CONFIG_TYPE flag to config_port call.
> 
> The same problem seems be to reported some time back to the maintainers which can be found in the link  - https://www.spinics.net/lists/linux-serial/msg29169.html. But the patch didn't make it through to the mainline kernel. Could you please let us know the resolution of that thread? Is it rejected/accepted?

That patch was from 2018, I can't remember what I reviewed last week :)

If it's not in the kernel tree today, then no, it was not accepted.  If
you need something like this, please test that patch and resend it with
your signed-off-by and we will be glad to review it.

thanks,

greg k-h

           reply	other threads:[~2020-12-11  8:42 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <DM6PR11MB2586CF444FFBF203D0709A5093CA0@DM6PR11MB2586.namprd11.prod.outlook.com>]

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=X9Mw7lNRo+rEpyFP@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=GaneshKumar.Gurumurthy@microchip.com \
    --cc=Kumaravel.Thiagarajan@microchip.com \
    --cc=LakshmiPraveen.Kopparthi@microchip.com \
    --cc=Muthukumar.Veeramani@microchip.com \
    --cc=Sundararaman.H@microchip.com \
    --cc=Woojung.Huh@microchip.com \
    --cc=linux-serial@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 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.