From: Greg KH <gregkh@linuxfoundation.org>
To: Jonathan Cameron <jic23@kernel.org>
Cc: linux-iio@vger.kernel.org
Subject: Re: [PULL] IIO: New device support, features and cleanup for 6.13
Date: Thu, 17 Oct 2024 20:14:36 +0200 [thread overview]
Message-ID: <2024101724-sandblast-petty-049d@gregkh> (raw)
In-Reply-To: <20241017183906.104ce8c1@jic23-huawei>
On Thu, Oct 17, 2024 at 06:39:06PM +0100, Jonathan Cameron wrote:
> On Thu, 17 Oct 2024 18:33:03 +0100
> Jonathan Cameron <jic23@kernel.org> wrote:
>
> > The following changes since commit 8cf0b93919e13d1e8d4466eb4080a4c4d9d66d7b:
> >
> > Linux 6.12-rc2 (2024-10-06 15:32:27 -0700)
> >
> > are available in the Git repository at:
> >
> > https://git.kernel.org/pub/scm/linux/kernel/git/jic23/iio.git tags/iio-for-6.13a
> >
> > for you to fetch changes up to f548c11a85ff08e3c6ac7fdf995cb98bf95c9acf:
> >
> > iio: light: rpr0521: Use generic iio_pollfunc_store_time() (2024-10-15 18:59:51 +0100)
>
> Hi Greg,
>
> Please ignore this. There is is a spurious empty file.
>
> However, given I've sent it.
>
> I wasn't 100% sure on how to generate a pull request when I had a merge
> of Linus' tree in the middle of it.
> Doing git request-pull v6.12-rc2 ....
> seemed to include all the right patches and makes sense to me, but if
> there is a better way do let me know.
As the tree I will be pulling into (char-misc-next), already has -rc2,
this should be just fine, right? The request-pull lines seem to show
that this is fine, so all should be good. I'll watch out for it when
you send the fixed-up pull-request.
thanks,
greg k-h
prev parent reply other threads:[~2024-10-17 18:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-17 17:33 [PULL] IIO: New device support, features and cleanup for 6.13 Jonathan Cameron
2024-10-17 17:39 ` Jonathan Cameron
2024-10-17 18:14 ` 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=2024101724-sandblast-petty-049d@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=jic23@kernel.org \
--cc=linux-iio@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox