Hi Greg,
On 2023-10-16 20:57:57+0200, [email protected] wrote:
>
> This is a note to let you know that I've just added the patch titled
>
> misc/pvpanic: deduplicate comomn code
It seems I managed to inject a typo into the commit subject:
s/comomn/common/
In case it's still possible and worth it, could you fix it up?
> to my char-misc git tree which can be found at
> git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/char-misc.git
> in the char-misc-testing branch.
>
> The patch will show up in the next release of the linux-next tree
> (usually sometime within the next 24 hours during the week.)
>
> The patch will be merged to the char-misc-next branch sometime soon,
> after it passes testing, and the merge window is open.
>
> If you have any questions about this process, please let me know.
Thanks,
Thomas
On Mon, Oct 16, 2023 at 09:06:39PM +0200, Thomas Wei?schuh wrote:
> Hi Greg,
>
> On 2023-10-16 20:57:57+0200, [email protected] wrote:
> >
> > This is a note to let you know that I've just added the patch titled
> >
> > misc/pvpanic: deduplicate comomn code
>
> It seems I managed to inject a typo into the commit subject:
>
> s/comomn/common/
>
> In case it's still possible and worth it, could you fix it up?
Nah, it's not worth rewriting history because of it. Unless the 0-day
bot finds problems with the tree, I'll just leave it as is.
thanks,
greg k-h
On Mon, Oct 16, 2023 at 09:06:39PM +0200, Thomas Wei?schuh wrote:
> Hi Greg,
>
> On 2023-10-16 20:57:57+0200, [email protected] wrote:
> >
> > This is a note to let you know that I've just added the patch titled
> >
> > misc/pvpanic: deduplicate comomn code
>
> It seems I managed to inject a typo into the commit subject:
>
> s/comomn/common/
>
> In case it's still possible and worth it, could you fix it up?
I ended up rebasing so I fixed this up, so no need to worry about it :)