public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Xu Yilun <yilun.xu@intel.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	Moritz Fischer <mdf@kernel.org>, Wu Hao <hao.wu@intel.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>,
	Matthew Gerlach <matthew.gerlach@linux.intel.com>,
	Randy Dunlap <rdunlap@infradead.org>
Subject: Re: linux-next: manual merge of the fpga tree with the tty tree
Date: Tue, 24 Jan 2023 18:01:55 +0100	[thread overview]
Message-ID: <Y9APAw4CoA31ubtb@kroah.com> (raw)
In-Reply-To: <Y9AKa/MU2EJPgQXS@yilunxu-OptiPlex-7050>

On Wed, Jan 25, 2023 at 12:42:19AM +0800, Xu Yilun wrote:
> On 2023-01-23 at 12:45:02 +1100, Stephen Rothwell wrote:
> > Hi all,
> > 
> > Today's linux-next merge of the fpga tree got conflicts in:
> > 
> >   drivers/fpga/dfl.c
> >   drivers/fpga/dfl.h
> > 
> > between commit:
> > 
> >   4747ab89b4a6 ("fpga: dfl: add basic support for DFHv1")
> > 
> > from the tty tree and commits:
> > 
> >   3afe90d5b7a4 ("fpga: dfl: kernel-doc corrections")
> >   e5541aae450e ("fpga: dfl: more kernel-doc corrections")
> > 
> > from the fpga tree.
> 
> 
> Hi Greg:
> 
> I could re-apply the 2 FPGA patches based on the following series on
> tty-next tree:
> 
> 46879f71061a ("Documentation: fpga: dfl: Add documentation for DFHv1")
> 0926d8d52d42 ("fpga: dfl: Add DFHv1 Register Definitions")
> 4747ab89b4a6 ("fpga: dfl: add basic support for DFHv1")
> e34a79d0b320 ("tty: serial: 8250: add DFL bus driver for Altera 16550")
> 
> Then there will be no conflict for my pull request.

Ok, that seems reasonable.  If there's anything you think I should
change in the tty tree, please let me know.

thanks,

greg k-h

      reply	other threads:[~2023-01-24 17:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-23  1:45 linux-next: manual merge of the fpga tree with the tty tree Stephen Rothwell
2023-01-24 16:42 ` Xu Yilun
2023-01-24 17:01   ` Greg KH [this message]

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=Y9APAw4CoA31ubtb@kroah.com \
    --to=greg@kroah.com \
    --cc=hao.wu@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=matthew.gerlach@linux.intel.com \
    --cc=mdf@kernel.org \
    --cc=rdunlap@infradead.org \
    --cc=sfr@canb.auug.org.au \
    --cc=yilun.xu@intel.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox